Triple
T9775114
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dan Carter |
E237225
|
entity |
| Predicate | playsKickingRole |
P68592
|
FINISHED |
| Object | goal-kicker |
—
|
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: goal-kicker | Statement: [Dan Carter, playsKickingRole, goal-kicker]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playsKickingRole Context triple: [Dan Carter, playsKickingRole, goal-kicker]
-
A.
playsInRole
Indicates that an entity performs or appears in a specific role within a production, event, or context.
-
B.
playRoleIn
chosen
Indicates that an entity participates in or performs a specific function, character, or part within an event, context, or system.
-
C.
playsAs
Indicates that one entity performs, portrays, or assumes the role, character, or persona of another entity.
-
D.
playedRoleIn
Indicates that an entity performed or assumed a specific role or character within a particular event, production, or context.
-
E.
playedKeyRoleIn
Indicates that an entity had a major, influential, or decisive impact on the occurrence, outcome, or success of another entity or event.
- 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_69ca84d975a08190aab25b02a89bdab3 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cda13148288190bcbb3b4a066d9fc1 |
completed | April 1, 2026, 10:50 p.m. |
| PD | Predicate disambiguation | batch_69cd03d3b68c81909e570401a891b9f2 |
completed | April 1, 2026, 11:38 a.m. |
Created at: March 30, 2026, 8:26 p.m.