Triple
T2753758
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NFL 1990s All-Decade Team |
E61051
|
entity |
| Predicate | positionIncluded |
P41662
|
FINISHED |
| Object | quarterback |
—
|
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: quarterback | Statement: [NFL 1990s All-Decade Team, positionIncluded, quarterback]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionIncluded Context triple: [NFL 1990s All-Decade Team, positionIncluded, quarterback]
-
A.
positionInCase
Indicates the specific role, status, or placement that an entity holds within a particular case or legal proceeding.
-
B.
positionOn
Indicates that one entity is located on top of or at a specific place along the surface or extent of another entity.
-
C.
isPositionOf
Indicates that one entity represents the spatial or organizational position or location of another entity.
-
D.
positionInState
Indicates that one entity occupies or holds a specific position, role, or status within a particular state or condition of another entity.
-
E.
positionSpecific
Indicates that something applies only at, or is defined with respect to, a particular position or location within a larger structure or sequence.
- 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_69ab4b7a85bc819094a349b84beb1f2c |
completed | March 6, 2026, 9:47 p.m. |
| NER | Named-entity recognition | batch_69abdb6ed9c08190824d1866e198ef80 |
completed | March 7, 2026, 8:01 a.m. |
| PD | Predicate disambiguation | batch_69abd82d005c81908a1ac7a1313c6d88 |
completed | March 7, 2026, 7:47 a.m. |
| PDg | Predicate description generation | batch_69abd91497ec8190927e91ad33549eda |
completed | March 7, 2026, 7:51 a.m. |
Created at: March 6, 2026, 9:56 p.m.