Triple
T423590
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Durham Bulls Athletic Park |
E8156
|
entity |
| Predicate | hasConcourseType |
P1656
|
FINISHED |
| Object | open concourse |
—
|
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: open concourse | Statement: [Durham Bulls Athletic Park, hasConcourseType, open concourse]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasConcourseType Context triple: [Durham Bulls Athletic Park, hasConcourseType, open concourse]
-
A.
hasConcourse
chosen
Indicates that an entity includes, is connected to, or is served by a concourse area (such as a passageway or central hall).
-
B.
hasConeType
Indicates that an entity possesses or is associated with a specific type or category of cone.
-
C.
hasCampType
Indicates that an entity is associated with or classified by a particular type or category of camp.
-
D.
hasStageType
Indicates that an entity is associated with, or classified by, a specific type or category of stage within a process, lifecycle, or workflow.
-
E.
hasProjectType
Indicates that an entity is associated with, or classified under, a specific type or category of project.
- 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_69a2e7f1d1bc81909cf2dc9754a3c334 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2eec200648190bcb9f1b98c8e9cdf |
completed | Feb. 28, 2026, 1:33 p.m. |
| PD | Predicate disambiguation | batch_69a2edd5439c8190aea661b8b4aa51e9 |
completed | Feb. 28, 2026, 1:29 p.m. |
Created at: Feb. 28, 2026, 1:11 p.m.