Triple
T7124444
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Assam State Zoo cum Botanical Garden |
E166024
|
entity |
| Predicate | botanicalGardenAdded |
P74997
|
FINISHED |
| Object | 1982 |
—
|
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: 1982 | Statement: [Assam State Zoo cum Botanical Garden, botanicalGardenAdded, 1982]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: botanicalGardenAdded Context triple: [Assam State Zoo cum Botanical Garden, botanicalGardenAdded, 1982]
-
A.
hasBotanicalGarden
Indicates that one entity possesses, contains, or includes a botanical garden as part of its facilities or domain.
-
B.
hasBotanicalGardenArea_ha
Indicates that an entity possesses a botanical garden whose area is measured in hectares.
-
C.
createdAsGarden
Indicates that something was brought into existence or established specifically in the form or function of a garden.
-
D.
isBotanical
Indicates that something pertains to plants or plant science, such as being derived from, related to, or characteristic of botanical life or botany.
-
E.
hasCommemorativePlanting
Indicates that an entity has a specific plant or planting established to commemorate or honor a person, event, or occasion.
- 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_69c6888350588190870cd552b427a1cd |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e64c0f688190a9b7482d86c2f033 |
completed | March 27, 2026, 8:19 p.m. |
| PD | Predicate disambiguation | batch_69c6e1c7289881909f3b533c384f9ed4 |
completed | March 27, 2026, 8 p.m. |
| PDg | Predicate description generation | batch_69c6e4a213508190a40aca39f9eee7d5 |
completed | March 27, 2026, 8:12 p.m. |
Created at: March 27, 2026, 2:44 p.m.