Triple
T10998193
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Government of Oregon Territory |
E259935
|
entity |
| Predicate | dateTerritoryReduced |
P96551
|
FINISHED |
| Object | 1853-03-02 |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: 1853-03-02 | Statement: [Government of Oregon Territory, dateTerritoryReduced, 1853-03-02]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dateTerritoryReduced Context triple: [Government of Oregon Territory, dateTerritoryReduced, 1853-03-02]
-
A.
reducedTerritoryOf
Indicates that one entity has caused a decrease in the size or extent of another entity's territory or area of control.
-
B.
calendarRegionOfOrigin
Indicates the geographic or cultural region from which a particular calendar system originates.
-
C.
nameDayRegion
Indicates the region or geographic area in which a particular name day is observed or recognized.
-
D.
countryOrTerritory
Indicates that one entity is a country or territory associated with, or characterized by, another entity.
-
E.
countryOrRegion
Indicates that one entity is a country or geographic region associated with another entity (such as its location, jurisdiction, or area of relevance).
- F. None of above. chosen
Provenance (4 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69d6aa8a6a548190a750f944ccdc8064 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d796d3b08c81909376cd73c42fcefe |
completed | April 9, 2026, 12:08 p.m. |
| PD | Predicate disambiguation | batch_69d72e93ac648190b46c5d12bf3eb1e9 |
completed | April 9, 2026, 4:44 a.m. |
| PDg | Predicate description generation | batch_69d732242fdc8190be77d1f730a42935 |
completed | April 9, 2026, 4:59 a.m. |
Created at: April 8, 2026, 9:24 p.m.