Triple
T7079471
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jay Heaps |
E164908
|
entity |
| Predicate | hasPlayedInPosition |
P11751
|
FINISHED |
| Object | right back |
—
|
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: right back | Statement: [Jay Heaps, hasPlayedInPosition, right back]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPlayedInPosition Context triple: [Jay Heaps, hasPlayedInPosition, right back]
-
A.
playsInPosition
chosen
Indicates that an entity (typically a player) performs or operates in a specific role or position within a game, sport, or activity.
-
B.
laterPlayedFor
Indicates that an individual was a member of or played for a team or organization at a time after a previously referenced team or organization.
-
C.
playedFor
Indicates that one entity has been a member of or participated as a player for a particular team, organization, or group.
-
D.
hasNotablePosition
Indicates that an entity holds or has held a position, role, or office considered notable or significant.
-
E.
playedInPeriod
Indicates that an entity participated or was active during a specified time period.
- 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_69c6887cbc6c8190bdfac42d940f4d8a |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e4ef47d48190b31125d1b57f7bec |
completed | March 27, 2026, 8:13 p.m. |
| PD | Predicate disambiguation | batch_69c6e1bfcb948190a5ada74fb8c054cb |
completed | March 27, 2026, 8 p.m. |
Created at: March 27, 2026, 2:40 p.m.