Triple
T6723591
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MIN |
E153454
|
entity |
| Predicate | scoreboardUsage |
P42512
|
FINISHED |
| Object | Displayed as MIN on MLB scoreboards |
—
|
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: Displayed as MIN on MLB scoreboards | Statement: [MIN, scoreboardUsage, Displayed as MIN on MLB scoreboards]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scoreboardUsage Context triple: [MIN, scoreboardUsage, Displayed as MIN on MLB scoreboards]
-
A.
hasScoreboard
Indicates that one entity is equipped with or associated with a scoreboard used to display scores or results.
-
B.
usedOnScoreboards
chosen
Indicates that something is employed or displayed specifically on scoreboards.
-
C.
scoreUsedFor
Indicates that a particular score or rating is used for a specific purpose, decision, or downstream process.
-
D.
hasScoreboardLocation
Indicates the spatial or logical position where a scoreboard is placed or associated within a given context.
-
E.
scoresWhen
Indicates that one entity achieves a score or points at the time or under the condition specified by another entity or 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_69c6880afb988190ad88011b48ecfcba |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d354177481908ab3cf5437c095e2 |
completed | March 27, 2026, 6:58 p.m. |
| PD | Predicate disambiguation | batch_69c6d08e8a2c8190ae4e8d8c039be7ce |
completed | March 27, 2026, 6:46 p.m. |
Created at: March 27, 2026, 2:08 p.m.