Triple
T6397783
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Répons |
E143982
|
entity |
| Predicate | yearOfFirstVersionCompletion |
P51515
|
FINISHED |
| Object | 1981 |
—
|
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: 1981 | Statement: [Répons, yearOfFirstVersionCompletion, 1981]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: yearOfFirstVersionCompletion Context triple: [Répons, yearOfFirstVersionCompletion, 1981]
-
A.
firstVersionYear
chosen
Indicates the calendar year in which the first version or initial release of something was created, published, or made available.
-
B.
developedSince
Indicates that something has been created, expanded, or advanced starting from a specified point in time and continuing thereafter.
-
C.
firstCompleterYear
Indicates the calendar or academic year in which an entity first completed a specified program, requirement, or activity.
-
D.
initialReleaseApprox
Indicates that an entity’s first release or debut occurred around an estimated or approximate point in time rather than on a precisely known date.
-
E.
firstDeployedAt
Indicates the date and time when an entity was initially put into use or made operational.
- 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_69c008dc56fc81908d43ffcc11d73bdd |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c06896d180819091548a728e903184 |
completed | March 22, 2026, 10:09 p.m. |
| PD | Predicate disambiguation | batch_69c060f25c088190b433f78553ff1d84 |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:35 p.m.