Triple
T16476114
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chuck Muncie |
E400190
|
entity |
| Predicate | touchdownsInSeason |
P70224
|
FINISHED |
| Object | 19 (1981 regular season rushing touchdowns) |
—
|
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: 19 (1981 regular season rushing touchdowns) | Statement: [Chuck Muncie, touchdownsInSeason, 19 (1981 regular season rushing touchdowns)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: touchdownsInSeason Context triple: [Chuck Muncie, touchdownsInSeason, 19 (1981 regular season rushing touchdowns)]
-
A.
rushingTouchdownsInSeason
chosen
Indicates the number of rushing touchdowns a player scores during a single season.
-
B.
touchdownsScored
Indicates the number of touchdowns that an entity has scored.
-
C.
touchdownPoints
Indicates the number of points awarded to a team for successfully scoring a touchdown in a game.
-
D.
scoredTouchdownIn
Indicates that an entity successfully achieved a touchdown during a specified game or event.
-
E.
singleSeasonTotalTouchdownsRecord
Indicates the record-setting highest number of touchdowns scored by an entity within a single 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_69d883813098819084f5409539723b59 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e32dd4f53081908f78b88435c8c719 |
completed | April 18, 2026, 7:08 a.m. |
| PD | Predicate disambiguation | batch_69e22706b0588190a48a951c5211a617 |
completed | April 17, 2026, 12:26 p.m. |
Created at: April 10, 2026, 5:13 a.m.