Triple
T423563
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Durham Bulls Athletic Park |
E8156
|
entity |
| Predicate | hasScoreboardFeature |
P182
|
FINISHED |
| Object | snorting bull sign |
—
|
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: snorting bull sign | Statement: [Durham Bulls Athletic Park, hasScoreboardFeature, snorting bull sign]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasScoreboardFeature Context triple: [Durham Bulls Athletic Park, hasScoreboardFeature, snorting bull sign]
-
A.
hasScoreboard
Indicates that one entity is equipped with or associated with a scoreboard used to display scores or results.
-
B.
hasScoreboardType
Indicates the specific kind or category of scoreboard associated with an entity.
-
C.
hasScoreboardLocation
Indicates the spatial or logical position where a scoreboard is placed or associated within a given context.
-
D.
hasFeature
chosen
Indicates that an entity possesses, exhibits, or includes a particular characteristic, attribute, or component.
-
E.
supportsFeature
Indicates that one entity provides, enables, or is compatible with a particular feature or capability of another.
- 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.