Triple
T19814916
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NH 1 (northern section) |
E476034
|
entity |
| Predicate | formerDesignationValidUntil |
P17450
|
FINISHED |
| Object | early 2010s |
—
|
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: early 2010s | Statement: [NH 1 (northern section), formerDesignationValidUntil, early 2010s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerDesignationValidUntil Context triple: [NH 1 (northern section), formerDesignationValidUntil, early 2010s]
-
A.
formerDesignation
Indicates that an entity previously held a particular title, role, or designation that it no longer holds.
-
B.
isTemporaryDesignation
Indicates that a given designation or label is intended to be used only for a limited time and is not the entity’s permanent or final designation.
-
C.
existedUntil
Indicates that an entity continued to exist up to, but not necessarily beyond, a specified time or event.
-
D.
deFactoEndDate
Indicates the date on which a relationship, status, or condition effectively ended in practice, regardless of any formal or official end date.
-
E.
formerNamePeriodEnd
chosen
Indicates the point in time when an entity stopped using a former name.
- 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_69d8e51bc4208190a1c57d8c5d1b15e4 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e654f861248190a633dd8d227d9697 |
completed | April 20, 2026, 4:31 p.m. |
| PD | Predicate disambiguation | batch_69e5305858108190bbbfdb9ba3ab9f80 |
completed | April 19, 2026, 7:43 p.m. |
Created at: April 10, 2026, 1:50 p.m.