Triple
T9925508
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IRDT |
E187911
|
entity |
| Predicate | historicallyObservedIn |
P91166
|
FINISHED |
| Object | 20th century |
—
|
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: 20th century | Statement: [IRDT, historicallyObservedIn, 20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicallyObservedIn Context triple: [IRDT, historicallyObservedIn, 20th century]
-
A.
historicallyNativeTo
Indicates that an entity has been originally or traditionally present in, or originating from, a particular place or region over a significant period in history.
-
B.
dstObservedHistorically
Indicates that something has been observed or recorded at a particular destination or location in the past.
-
C.
countryObservedIn
Indicates that an entity has been observed or recorded within the geographical boundaries of a specified country.
-
D.
historicallyBasedIn
Indicates that one entity is located in or associated with a place as its base of operations during a specific historical period.
-
E.
historicallyAdoptedBy
Indicates that something (such as a practice, policy, idea, or object) was used or taken up by an entity at some point in the past.
- 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_69ca82b22a688190b52c75bd48429c10 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cdb599e32c8190ac676fa89c131bb6 |
completed | April 2, 2026, 12:17 a.m. |
| PD | Predicate disambiguation | batch_69cd1d90b8a8819081748f129c0c6ab6 |
completed | April 1, 2026, 1:28 p.m. |
| PDg | Predicate description generation | batch_69cd3581a9688190a00cef4c3eebb0ae |
completed | April 1, 2026, 3:10 p.m. |
Created at: March 30, 2026, 8:43 p.m.