Triple
T27262620
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tamil Nadu Engineering Admissions |
E687806
|
entity |
| Predicate | adminOfficeLocation |
P39747
|
FINISHED |
| Object | Chennai |
—
|
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 | Statement: [Tamil Nadu Engineering Admissions, adminOfficeLocation, Chennai]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: adminOfficeLocation Context triple: [Tamil Nadu Engineering Admissions, adminOfficeLocation, Chennai]
-
A.
administrativeOffice
chosen
Indicates that one entity serves as the administrative office or central administrative unit responsible for managing or overseeing the affairs of another entity.
-
B.
collectorOfficeLocation
Indicates the physical office location associated with a particular collector.
-
C.
adminCenterLocatedOn
Indicates that the administrative center of an entity is situated on or within a specified geographic or physical feature.
-
D.
addressesOffice
Indicates that one entity directs communication, correspondence, or attention specifically to an office associated with another entity.
-
E.
officeDeskLocation
Indicates the specific desk or workstation location assigned to or used by an entity within an office space.
- 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_69ef3557abc481908bf3c146f0f3356a |
completed | April 27, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69f71422adac8190a5ceb32dcf820833 |
completed | May 3, 2026, 9:23 a.m. |
| PD | Predicate disambiguation | batch_69f712764d2c819081b64b27e5de4a13 |
completed | May 3, 2026, 9:16 a.m. |
Created at: April 27, 2026, 10:53 a.m.