Triple
T2993870
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NFL 100th Anniversary All-Time Team |
E81019
|
entity |
| Predicate | positionGroups |
P29748
|
FINISHED |
| Object | quarterbacks |
—
|
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: quarterbacks | Statement: [NFL 100th Anniversary All-Time Team, positionGroups, quarterbacks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionGroups Context triple: [NFL 100th Anniversary All-Time Team, positionGroups, quarterbacks]
-
A.
positionGroup
chosen
Indicates a grouping relationship where multiple positions or roles are collectively associated or organized under a common group.
-
B.
boardingGroups
Indicates that certain entities are assigned to or associated with specific boarding groups for an ordered boarding process.
-
C.
letterGroups
Indicates that entities are organized or associated into specific groups based on letters or letter-based criteria.
-
D.
targetsGroup
Indicates that an action, influence, or effect is directed toward a specific group as its intended recipient or focus.
-
E.
positionClass
Indicates the classification or category assigned to an entity based on its role, rank, or position within a defined structure or system.
- 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_69ad8b187fc8819085914d3c9ea3142d |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad99e291e0819089f81c0a7d7a6cd9 |
completed | March 8, 2026, 3:46 p.m. |
| PD | Predicate disambiguation | batch_69ad961403108190bbecb8d3608fd4e0 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 2:59 p.m.