Triple
T18271148
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Team USA |
E437616
|
entity |
| Predicate | captainRole |
P31052
|
FINISHED |
| Object | non‑playing captain |
—
|
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: non‑playing captain | Statement: [Team USA, captainRole, non‑playing captain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: captainRole Context triple: [Team USA, captainRole, non‑playing captain]
-
A.
captain
Indicates that one entity serves as the leader or person in command of another entity, typically a team, group, or vessel.
-
B.
captainPosition
chosen
Indicates that an entity holds the role or position of captain in relation to another entity (such as a team, vessel, or group).
-
C.
coCaptain
Indicates that two or more individuals share the role and responsibilities of captain jointly.
-
D.
laterCaptain
Indicates that one entity becomes the captain of something at a later time than another referenced captain or captaincy.
-
E.
captainDuringEvent
Indicates that an entity serves as the captain of a team, group, or vessel for the duration of a specified 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_69d8b913351c8190932b6a426de04b41 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4ff7e00548190a28916a696831336 |
completed | April 19, 2026, 4:14 p.m. |
| PD | Predicate disambiguation | batch_69e44fd81c788190b08c6be3b07a08c5 |
completed | April 19, 2026, 3:45 a.m. |
Created at: April 10, 2026, 10:34 a.m.