Triple
T10518521
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1987 NFL season |
E248100
|
entity |
| Predicate | replacementPlayersUsed |
P94351
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [1987 NFL season, replacementPlayersUsed, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: replacementPlayersUsed Context triple: [1987 NFL season, replacementPlayersUsed, true]
-
A.
replacedPlayer
Indicates that one player has been substituted out of play and replaced by another player.
-
B.
hasRetiredPlayersFrom
Indicates that an entity has players who previously played for it and have since retired, originating from the specified source entity (e.g., team, league, or country).
-
C.
managedPlayers
Indicates that one entity has managerial responsibility or authority over the players represented by the other entity.
-
D.
replacementMember
Indicates that one entity serves as a substitute or successor taking over the role, position, or function previously held by another entity.
-
E.
substitutesPerTeam
Indicates the number of substitute players allowed or used by each team in a given context.
- 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_69d381c4aa948190942e1d803143fb0e |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d509dd29b48190aa5b170e2558545c |
completed | April 7, 2026, 1:42 p.m. |
| PD | Predicate disambiguation | batch_69d4fb94fa10819091f585bab4379c6f |
completed | April 7, 2026, 12:41 p.m. |
| PDg | Predicate description generation | batch_69d4fe06d4a48190b1a45dd1d4e16df0 |
completed | April 7, 2026, 12:52 p.m. |
Created at: April 6, 2026, 12:28 p.m.