Triple
T8357873
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reval |
E196723
|
entity |
| Predicate | timePeriodAsOfficialNameEnd |
P17450
|
FINISHED |
| Object | 1918 |
—
|
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: 1918 | Statement: [Reval, timePeriodAsOfficialNameEnd, 1918]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timePeriodAsOfficialNameEnd Context triple: [Reval, timePeriodAsOfficialNameEnd, 1918]
-
A.
timePeriodEndApprox
Indicates that the associated time period ends at an approximate, rather than exact, point in time.
-
B.
governedPeriodEnd
Indicates the point in time at which a governing authority’s control or jurisdiction over something comes to an end.
-
C.
endDateOfficialUse
Indicates the date on which the official use or validity of something (such as a document, status, or authorization) comes to an end.
-
D.
formerNamePeriodEnd
chosen
Indicates the point in time when an entity stopped using a former name.
-
E.
timePeriodAsSeatOfGovernmentEnd
Indicates the point in time when a particular location ceases to serve as the seat of government for an entity.
- 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_69ca82f08b348190bfb7881944bbff6f |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb806fa5c88190b23b6b3ee9d6ec6d |
completed | March 31, 2026, 8:06 a.m. |
| PD | Predicate disambiguation | batch_69cb70ca25548190b0f90c5384e3fb3c |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 5:59 p.m.