Triple
T16114504
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North Carolina Zoo |
E390966
|
entity |
| Predicate | visitorService |
P121527
|
FINISHED |
| Object | tram transportation within the park |
—
|
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: tram transportation within the park | Statement: [North Carolina Zoo, visitorService, tram transportation within the park]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: visitorService Context triple: [North Carolina Zoo, visitorService, tram transportation within the park]
-
A.
visitorPractice
Indicates that a visitor engages in or performs a particular practice, activity, or routine.
-
B.
visitorIs
Indicates that one entity is acting in the role or capacity of a visitor with respect to another entity.
-
C.
visitor
Indicates that one entity is present at or attending another entity’s location, event, or context as a non-permanent guest.
-
D.
visitorUse
Indicates that an entity is being used, accessed, or engaged with by a visitor or temporary user.
-
E.
visitorStatus
Indicates the current state or condition of an entity in its role as a visitor (e.g., whether they are active, pending, past, or otherwise classified in their visit).
- 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_69d87f1a8dd881909f1de6ef78849874 |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e20169ce488190bbc814f23a3b7547 |
completed | April 17, 2026, 9:46 a.m. |
| PD | Predicate disambiguation | batch_69e1828518c48190a8ef3aaa46a1f639 |
completed | April 17, 2026, 12:44 a.m. |
| PDg | Predicate description generation | batch_69e183b9d3f08190953ada68f4272996 |
completed | April 17, 2026, 12:50 a.m. |
Created at: April 10, 2026, 5 a.m.