Triple
T9480966
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paul Wiggin |
E228634
|
entity |
| Predicate | playedPositionGroup |
P29748
|
FINISHED |
| Object | defensive line |
—
|
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: defensive line | Statement: [Paul Wiggin, playedPositionGroup, defensive line]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playedPositionGroup Context triple: [Paul Wiggin, playedPositionGroup, defensive line]
-
A.
playingPosition
Indicates the specific role or position an individual occupies while participating in a game or sport.
-
B.
playsInPosition
Indicates that an entity (typically a player) performs or operates in a specific role or position within a game, sport, or activity.
-
C.
positionGroup
chosen
Indicates a grouping relationship where multiple positions or roles are collectively associated or organized under a common group.
-
D.
movementGrouping
Indicates that multiple movements or motion events are treated as a single grouped or coordinated unit within a larger action or process.
-
E.
playedFrom
Indicates that an action of playing (such as media playback or a performance) originated from a particular source or starting point.
- 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_69ca84730a5081908de282651019bf2f |
completed | March 30, 2026, 2:10 p.m. |
| NER | Named-entity recognition | batch_69cd8018645c8190823d82a93635b345 |
completed | April 1, 2026, 8:29 p.m. |
| PD | Predicate disambiguation | batch_69cca561e6b0819090aa795f3c3a2083 |
completed | April 1, 2026, 4:56 a.m. |
Created at: March 30, 2026, 7:54 p.m.