Triple
T10881336
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Northern Trek |
E256924
|
entity |
| Predicate | locatedInZooSection |
P22356
|
FINISHED |
| Object | Northern Trek area of Cleveland Metroparks Zoo |
—
|
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: Northern Trek area of Cleveland Metroparks Zoo | Statement: [Northern Trek, locatedInZooSection, Northern Trek area of Cleveland Metroparks Zoo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInZooSection Context triple: [Northern Trek, locatedInZooSection, Northern Trek area of Cleveland Metroparks Zoo]
-
A.
zooSection
chosen
Indicates that one entity is a specific section or area within a zoo where the other entity is located, organized, or assigned.
-
B.
zooSectionType
Indicates the specific type or category of section within a zoo that an area or enclosure belongs to.
-
C.
zooLocation
Indicates that a zoo is located in or associated with a specific geographic place or administrative area.
-
D.
zooType
Indicates the classification or category of a zoo, such as its type or kind.
-
E.
hasZoo
Indicates that one entity possesses, operates, or is associated with a zoo.
- 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_69d6aa848804819081b2713ca0bedf06 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d751da559c819094c3680a9f734ee7 |
completed | April 9, 2026, 7:14 a.m. |
| PD | Predicate disambiguation | batch_69d70d360c388190a3d829fe8862434f |
completed | April 9, 2026, 2:21 a.m. |
Created at: April 8, 2026, 9:21 p.m.