Triple
T4456422
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Miami Orange Bowl |
E97735
|
entity |
| Predicate | scoreboardFeature |
P2583
|
FINISHED |
| Object | famous end-zone scoreboard |
—
|
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: famous end-zone scoreboard | Statement: [Miami Orange Bowl, scoreboardFeature, famous end-zone scoreboard]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scoreboardFeature Context triple: [Miami Orange Bowl, scoreboardFeature, famous end-zone scoreboard]
-
A.
hasScoreboard
chosen
Indicates that one entity is equipped with or associated with a scoreboard used to display scores or results.
-
B.
usedOnScoreboards
Indicates that something is employed or displayed specifically on scoreboards.
-
C.
hasScoreboardLocation
Indicates the spatial or logical position where a scoreboard is placed or associated within a given context.
-
D.
isScoreFor
Indicates that one value represents the score or result associated with a particular entity, event, or performance.
-
E.
teamScoring
Indicates that a team achieves a score or points in a game, match, or competitive event.
- 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_69b3454777808190b78aa9047ba1f018 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b3564216b081908c41109100b36862 |
completed | March 13, 2026, 12:11 a.m. |
| PD | Predicate disambiguation | batch_69b34f649df081909d3cc2f6a1b8f282 |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:33 p.m.