Triple
T938973
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USS Alfred |
E20260
|
entity |
| Predicate | hasCrewRole |
P21967
|
FINISHED |
| Object | 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: captain | Statement: [USS Alfred, hasCrewRole, captain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCrewRole Context triple: [USS Alfred, hasCrewRole, captain]
-
A.
crew
Indicates that one entity serves as the group of people who operate, staff, or work on another entity (such as a vehicle, vessel, or production).
-
B.
playedBy
Indicates that a role, character, or performance is portrayed or executed by a specific person or agent.
-
C.
hasMainRole
Indicates that an entity holds the primary or most significant role in relation to another entity or context.
-
D.
playedRoleIn
Indicates that an entity performed or assumed a specific role or character within a particular event, production, or context.
-
E.
notableCastMember
Indicates that an entity is a member of the cast of another entity (such as a film, show, or production) and is considered particularly notable or significant in that role.
- F. None of above. chosen
Provenance (4 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_69a493b0270c81909e6c9ce310f6aa55 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4b38a3ad4819080d71849e822a12a |
completed | March 1, 2026, 9:45 p.m. |
| PD | Predicate disambiguation | batch_69a4b29c68f48190aecad10e351a99de |
completed | March 1, 2026, 9:41 p.m. |
| PDg | Predicate description generation | batch_69a4b344f6f48190ba03ce593c94176b |
completed | March 1, 2026, 9:44 p.m. |
Created at: March 1, 2026, 7:40 p.m.