Triple
T29681973
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Team Durant |
E750975
|
entity |
| Predicate | captainStatus |
P51184
|
FINISHED |
| Object | injured and did not play |
—
|
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: injured and did not play | Statement: [Team Durant, captainStatus, injured and did not play]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: captainStatus Context triple: [Team Durant, captainStatus, injured and did not play]
-
A.
crewStatus
chosen
Indicates the current operational or role-related condition of a crew member or crew group within a mission or organization.
-
B.
assistantCaptain
Indicates that one entity serves as the assistant or deputy to another entity who holds the role of captain.
-
C.
coCaptain
Indicates that two or more individuals share the role and responsibilities of captain jointly.
-
D.
statusOfLeadShip
Indicates the current condition or state assigned to the primary or leading ship in a given context or operation.
-
E.
captain
Indicates that one entity serves as the leader or person in command of another entity, typically a team, group, or vessel.
- 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_69f0d624d7b08190ba237d226f78d0d9 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f67f7efc3c8190986d2d95b7a23729 |
completed | May 2, 2026, 10:49 p.m. |
| PD | Predicate disambiguation | batch_69f67e40af9881908de3a4aa15f70a83 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 28, 2026, 7:10 p.m.