Triple
T22830977
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Indiana Pacers 1987–2005 |
E565799
|
entity |
| Predicate | positionOfMainFigure |
P149895
|
FINISHED |
| Object | shooting guard |
—
|
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: shooting guard | Statement: [Indiana Pacers 1987–2005, positionOfMainFigure, shooting guard]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionOfMainFigure Context triple: [Indiana Pacers 1987–2005, positionOfMainFigure, shooting guard]
-
A.
movementCentralFigure
Indicates that an entity serves as the primary or leading figure within a particular movement.
-
B.
positionInCase
Indicates the specific role, status, or placement that an entity holds within a particular case or legal proceeding.
-
C.
hasCentralFigure
Indicates that something features a primary or most important figure at its core or focus.
-
D.
positionDepicted
Indicates that one entity visually represents or depicts the spatial position or placement of another entity.
-
E.
positionOnKing
Indicates that one entity occupies a specific positional relationship relative to a king 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_69e24585ab1c81909b2b5065d15805d5 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17e2bcad8819091f237fd2273a20c |
completed | April 29, 2026, 3:42 a.m. |
| PD | Predicate disambiguation | batch_69eed2d117088190acbfe130d84f8627 |
completed | April 27, 2026, 3:06 a.m. |
| PDg | Predicate description generation | batch_69eeeb577e2081909f4a4e9c296535c0 |
completed | April 27, 2026, 4:51 a.m. |
Created at: April 17, 2026, 3:34 p.m.