Triple
T3589532
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Philly Special |
E75992
|
entity |
| Predicate | scoreBeforePlay |
P49537
|
FINISHED |
| Object | Philadelphia 15 – New England 12 |
—
|
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: Philadelphia 15 – New England 12 | Statement: [Philly Special, scoreBeforePlay, Philadelphia 15 – New England 12]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scoreBeforePlay Context triple: [Philly Special, scoreBeforePlay, Philadelphia 15 – New England 12]
-
A.
seriesScoreBeforeGame
Indicates the cumulative score or standing in a series between competitors as it existed prior to a specific game being played.
-
B.
scoreUsedFor
Indicates that a particular score or rating is used for a specific purpose, decision, or downstream process.
-
C.
seriesScoreAfterGame
Indicates the updated score or standing of a multi-game series immediately following the completion of a specific game.
-
D.
scoreScale
Indicates the scale or range on which a score or rating is expressed or measured.
-
E.
scoring
Indicates the act of achieving points or a measurable result, typically by successfully completing an action that contributes to a score or outcome.
- 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_69ad85d8042081908af94a04c410dec0 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc13c9514819096adf60b15016b8b |
completed | March 8, 2026, 6:34 p.m. |
| PD | Predicate disambiguation | batch_69adb839b4e08190b1c0d611cccb11ae |
completed | March 8, 2026, 5:56 p.m. |
| PDg | Predicate description generation | batch_69adb902e61c81908f10494f828e260f |
completed | March 8, 2026, 5:59 p.m. |
Created at: March 8, 2026, 3:22 p.m.