Triple
T11003450
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Indian Institute of Technology Delhi |
E260055
|
entity |
| Predicate | chancellorEquivalentTitle |
P3394
|
FINISHED |
| Object | Visitor |
—
|
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: Visitor | Statement: [Indian Institute of Technology Delhi, chancellorEquivalentTitle, Visitor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: chancellorEquivalentTitle Context triple: [Indian Institute of Technology Delhi, chancellorEquivalentTitle, Visitor]
-
A.
chancellorTitle
chosen
Indicates the official title or designation held by an individual serving in the role of chancellor.
-
B.
hasMinisterTitle
Indicates that an entity holds or is associated with a specific ministerial title or office.
-
C.
chancellorPower
Indicates that an entity holds the authoritative executive or administrative powers associated with the role of chancellor over another entity or domain.
-
D.
hasChancellor
Indicates that an entity holds the position or role of chancellor for another entity.
-
E.
precededInOfficeAsChancellorBy
Indicates that one individual assumed the role of Chancellor after another specific individual, who held the office immediately before them.
- 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_69d6aa8a6a548190a750f944ccdc8064 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d797546f448190946ee6442d657dc5 |
completed | April 9, 2026, 12:11 p.m. |
| PD | Predicate disambiguation | batch_69d72e96be6c8190a46c69f61b2d8cd4 |
completed | April 9, 2026, 4:44 a.m. |
Created at: April 8, 2026, 9:25 p.m.