Triple
T32177580
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TN-01 |
E821895
|
entity |
| Predicate | RTOName |
P744
|
FINISHED |
| Object | Chennai (Santhome) RTO |
—
|
NE NERFINISHED |
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: Chennai (Santhome) RTO | Statement: [TN-01, RTOName, Chennai (Santhome) RTO]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: RTOName Context triple: [TN-01, RTOName, Chennai (Santhome) RTO]
-
A.
RANName
Indicates that an entity has a specific Radio Access Network (RAN) name assigned to it.
-
B.
ROAFullName
Indicates that one entity is the full, expanded name corresponding to an abbreviated or shortened form represented by the other entity.
-
C.
nameOf
chosen
Indicates that one entity is the name or designation of another entity.
-
D.
registryName
Indicates that an entity is identified or labeled by a specific name within a registry or registration system.
-
E.
runtimeName
Indicates the name of the runtime environment or platform under which an entity (such as a program or process) is executed.
- 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_69f3490755288190aee11740a34862f9 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6ba7b13b481908a3658adff04878c |
completed | May 3, 2026, 3:01 a.m. |
| PD | Predicate disambiguation | batch_69f6b3aa892481908d29283a074e6722 |
completed | May 3, 2026, 2:32 a.m. |
Created at: May 1, 2026, 12:34 a.m.