Triple
T25398391
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | pre-2010 Indian national highway numbering |
E636353
|
entity |
| Predicate | stillReferencedIn |
P8581
|
FINISHED |
| Object | older government documents |
—
|
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: older government documents | Statement: [pre-2010 Indian national highway numbering, stillReferencedIn, older government documents]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stillReferencedIn Context triple: [pre-2010 Indian national highway numbering, stillReferencedIn, older government documents]
-
A.
isReferencedIn
chosen
Indicates that one entity is cited, mentioned, or otherwise referred to within another entity.
-
B.
stillUsedBy
Indicates that something continues to be used or relied upon by another entity at the present time.
-
C.
stillExists
Indicates that the referenced entity continues to exist or remain in effect at the current point in time.
-
D.
stillCitedFor
Indicates that a work or source continues to be referenced or relied upon as a citation after its original publication or use.
-
E.
hasReferences
Indicates that one entity cites, points to, or relies on another entity as a reference or source.
- 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_69e75db263888190b77fff9e2827b9a2 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f584f728fc8190982b260fa700002c |
completed | May 2, 2026, 5 a.m. |
| PD | Predicate disambiguation | batch_69f4683b34748190818428489a226124 |
completed | May 1, 2026, 8:45 a.m. |
Created at: April 21, 2026, 1:50 p.m.