Triple
T6672814
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chace |
E151771
|
entity |
| Predicate | associatedWithEraOfBearer |
P45464
|
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: [Chace, associatedWithEraOfBearer, 20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithEraOfBearer Context triple: [Chace, associatedWithEraOfBearer, 20th century]
-
A.
timePeriodOfNotableBearer
chosen
Indicates the span of time during which a notable bearer is recognized as having held, embodied, or been associated with the subject.
-
B.
appliesToEra
Indicates that something is relevant, valid, or in effect during a particular historical or temporal era.
-
C.
representsEra
Indicates that one entity designates the historical era, period, or age to which another entity belongs or is associated.
-
D.
associatedWithPlayerEra
Indicates a relationship where something is linked or connected to a specific era or period in a player's career.
-
E.
partOfEra
Indicates that one entity exists as a temporal segment or component within the duration or scope of a larger historical era.
- F. None of above.
Provenance (3 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_69c687f71fc081909dbd45d6377f6045 |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6ce738fe88190a5557900efeec7ec |
completed | March 27, 2026, 6:37 p.m. |
| PD | Predicate disambiguation | batch_69c6ad09974c81908784300ae218961f |
completed | March 27, 2026, 4:15 p.m. |
Created at: March 27, 2026, 2:03 p.m.