Triple
T12016272
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pro Football Hall of Fame All-1950s Team |
E286033
|
entity |
| Predicate | includesPositionGroup |
P29748
|
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: [Pro Football Hall of Fame All-1950s Team, includesPositionGroup, quarterback]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesPositionGroup Context triple: [Pro Football Hall of Fame All-1950s Team, includesPositionGroup, quarterback]
-
A.
positionGroup
chosen
Indicates a grouping relationship where multiple positions or roles are collectively associated or organized under a common group.
-
B.
positionIncluded
Indicates that one position or spatial region is entirely contained within another position or spatial region.
-
C.
includesCommonGroups
Indicates that two entities share at least one group or category in common.
-
D.
componentPosition
Indicates the spatial or logical placement of a component relative to a larger structure or system.
-
E.
ISOGroupingStatus
Indicates the relationship between an entity and its classification or status within an ISO-defined grouping or category.
- 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_69d6ab45a368819084fce08bf0dc3705 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d9100b4ca8819084845ca4c13e34ce |
completed | April 10, 2026, 2:58 p.m. |
| PD | Predicate disambiguation | batch_69d902b6ebbc8190b13c44a61c6f81b9 |
completed | April 10, 2026, 2:01 p.m. |
Created at: April 8, 2026, 9:47 p.m.