Triple
T35432542
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Autumn |
E1024101
|
entity |
| Predicate | enteredCommonUse |
P185261
|
FINISHED |
| Object | late 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: late 20th century | Statement: [Autumn, enteredCommonUse, late 20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: enteredCommonUse Context triple: [Autumn, enteredCommonUse, late 20th century]
-
A.
hasCommonRoomEntranceType
Indicates that two or more rooms share the same type or style of entrance.
-
B.
enteredInto
Indicates that one entity has initiated or become formally involved in a particular state, agreement, relationship, or situation with another entity.
-
C.
enteredSpace
Indicates that an entity has moved into or crossed the boundary into a particular space or area.
-
D.
hasAmenityAccessTo
Indicates that an entity has the right or ability to use or benefit from a specified amenity or facility.
-
E.
enterAs
Indicates that one entity goes into or joins another context, place, or role in the capacity or form specified.
- 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_69f76df743c48190aecb6dd79efb0d95 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7bbf906d8819099020e548dd56bc9 |
completed | May 3, 2026, 9:19 p.m. |
| PD | Predicate disambiguation | batch_69f7b9a2dcf88190a7c9e109e41267be |
completed | May 3, 2026, 9:09 p.m. |
| PDg | Predicate description generation | batch_69f7bbf812cc8190a16917c5daaff2df |
completed | May 3, 2026, 9:19 p.m. |
Created at: May 3, 2026, 4:03 p.m.