Triple
T7424712
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paycom Center |
E171338
|
entity |
| Predicate | scoreboardUpgrade |
P76898
|
FINISHED |
| Object | 2012 |
—
|
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: 2012 | Statement: [Paycom Center, scoreboardUpgrade, 2012]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scoreboardUpgrade Context triple: [Paycom Center, scoreboardUpgrade, 2012]
-
A.
hasScoreboard
Indicates that one entity is equipped with or associated with a scoreboard used to display scores or results.
-
B.
includesNewScoreBy
Indicates that an entity incorporates or contains a newly added score produced by another entity.
-
C.
scoresWhen
Indicates that one entity achieves a score or points at the time or under the condition specified by another entity or event.
-
D.
scoreScale
Indicates the scale or range on which a score or rating is expressed or measured.
-
E.
scoringRecord
Indicates that there exists a record documenting a scoring event or outcome associated with the given entities.
- 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_69c68a625d048190af70eb8b63bec5a0 |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f302b33481908eae877970f2bbdf |
completed | March 27, 2026, 9:13 p.m. |
| PD | Predicate disambiguation | batch_69c6f03648d08190b862d07fef71210c |
completed | March 27, 2026, 9:01 p.m. |
| PDg | Predicate description generation | batch_69c6f1ee5ab8819091082324f2dc3b8c |
completed | March 27, 2026, 9:09 p.m. |
Created at: March 27, 2026, 3:12 p.m.