Triple
T14047392
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vandalur |
E337992
|
entity |
| Predicate | zooSignificance |
P112611
|
FINISHED |
| Object | one of the largest zoological parks in India |
—
|
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: one of the largest zoological parks in India | Statement: [Vandalur, zooSignificance, one of the largest zoological parks in India]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: zooSignificance Context triple: [Vandalur, zooSignificance, one of the largest zoological parks in India]
-
A.
zooUsedFor
Indicates that a zoo serves a particular purpose, function, or use for something or someone.
-
B.
zooAccreditation
Indicates that an entity (such as a zoo or aquarium) holds a formal accreditation or certification from a recognized accrediting organization.
-
C.
zooSpecialization
Indicates that one entity is a zoo whose primary focus or expertise is specialized in the type, category, or group represented by the other entity.
-
D.
zooSection
Indicates that one entity is a specific section or area within a zoo where the other entity is located, organized, or assigned.
-
E.
zooType
Indicates the classification or category of a zoo, such as its type or kind.
- F. None of above. chosen
Provenance (4 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_69d81c664e48819088cbd8f433aeffe5 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de3c88b5e48190b0f0149102c08992 |
completed | April 14, 2026, 1:09 p.m. |
| PD | Predicate disambiguation | batch_69de05ab36b48190920efb1869bdb1fe |
completed | April 14, 2026, 9:15 a.m. |
| PDg | Predicate description generation | batch_69de2398856c81908bed6070e4ca6ab1 |
completed | April 14, 2026, 11:23 a.m. |
Created at: April 9, 2026, 10:20 p.m.