Triple
T8603150
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chandler Jones |
E203726
|
entity |
| Predicate | positionSwitch |
P49285
|
FINISHED |
| Object | moved between defensive end and outside linebacker in the NFL |
—
|
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: moved between defensive end and outside linebacker in the NFL | Statement: [Chandler Jones, positionSwitch, moved between defensive end and outside linebacker in the NFL]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionSwitch Context triple: [Chandler Jones, positionSwitch, moved between defensive end and outside linebacker in the NFL]
-
A.
positionChange
chosen
Indicates a change in an entity’s spatial or positional state from one location or configuration to another.
-
B.
positionUse
Indicates how a particular position or role is utilized or functionally applied within a given context.
-
C.
positionInCase
Indicates the specific role, status, or placement that an entity holds within a particular case or legal proceeding.
-
D.
switchesPlacesWith
Indicates that two entities exchange their respective positions or roles with each other.
-
E.
partySwitch
Indicates that an entity changes its affiliation from one political party to another.
- 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_69ca832b56948190ba751cec255308f1 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cc46dc23448190a5eb63455578427e |
completed | March 31, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69cc454eb2908190acf0e4336bc67e7b |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:24 p.m.