Triple
T29990483
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pittsburgh Power |
E761862
|
entity |
| Predicate | seasonRecord2014 |
P21379
|
FINISHED |
| Object | 15–3 |
—
|
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: 15–3 | Statement: [Pittsburgh Power, seasonRecord2014, 15–3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: seasonRecord2014 Context triple: [Pittsburgh Power, seasonRecord2014, 15–3]
-
A.
2014Record
Indicates that an entity holds or is associated with a record or achievement specifically from the year 2014.
-
B.
seasonRecord
chosen
Indicates the overall performance or results an entity achieved over the course of a specific season (e.g., wins, losses, or comparable outcome metrics).
-
C.
ALTeamRegularSeasonRecord
Indicates the relationship that specifies a team's win–loss record during the American League regular season.
-
D.
seasonRecordWins
Indicates the number of games a team has won during a specific season.
-
E.
awayTeamRegularSeasonRecord
Indicates the win-loss (and possibly tie) record that the away team has accumulated during the regular season.
- 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_69f224695498819094a81037cad401e2 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f7aa699d68819081ed363931894ab3 |
completed | May 3, 2026, 8:04 p.m. |
| PD | Predicate disambiguation | batch_69f7a8cec6d48190bebfa884b2f938c0 |
completed | May 3, 2026, 7:58 p.m. |
Created at: April 29, 2026, 6:38 p.m.