Triple
T14303336
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Orenburg |
E354624
|
entity |
| Predicate | dateOfRestoredName |
P17995
|
FINISHED |
| Object | 1957 |
—
|
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: 1957 | Statement: [Orenburg, dateOfRestoredName, 1957]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dateOfRestoredName Context triple: [Orenburg, dateOfRestoredName, 1957]
-
A.
dateRestoredName
chosen
Indicates the date on which a previously changed or removed name was restored to its former or original form.
-
B.
nameRestored
Indicates that an entity’s original or correct name has been reinstated after having been changed, lost, or altered.
-
C.
wasRestoredAt
Indicates that an entity was brought back to a previous or improved state at a specific time or place.
-
D.
reconstructionOrRestorationDate
Indicates the date on which an entity was reconstructed or restored after damage, alteration, or deterioration.
-
E.
nameChangeDate
Indicates the date on which an entity’s name was officially changed.
- 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_69d8278e17088190b328c5a9d4be74ff |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de717fc2348190bb6ba3109bd2871f |
completed | April 14, 2026, 4:55 p.m. |
| PD | Predicate disambiguation | batch_69de2a8f81f08190af737e1654847aa6 |
completed | April 14, 2026, 11:52 a.m. |
Created at: April 10, 2026, 1:12 a.m.