Triple
T24143580
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vasily Borodin |
E598310
|
entity |
| Predicate | partOfCrew |
P94498
|
FINISHED |
| Object | crew of Red October |
—
|
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: crew of Red October | Statement: [Vasily Borodin, partOfCrew, crew of Red October]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partOfCrew Context triple: [Vasily Borodin, partOfCrew, crew of Red October]
-
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.
crewOnboard
chosen
Indicates that a person or group is serving as crew aboard a specific vehicle, vessel, or craft.
-
C.
hasCrewRole
Indicates that an entity serves in a specific role or position within a crew associated with another entity.
-
D.
crewType
Indicates the specific role or category of crew associated with an entity, such as the type of personnel assigned to operate or support it.
-
E.
coCrewMember
Indicates that two or more individuals serve together as members of the same crew on a shared mission, vehicle, or operation.
- 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_69e288c92e448190ac57034fa0c863ce |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1e008efbc8190ac6c12d3ba5dd5d8 |
completed | April 29, 2026, 10:40 a.m. |
| PD | Predicate disambiguation | batch_69f1765650fc8190a6bc1eb512b240bf |
completed | April 29, 2026, 3:09 a.m. |
Created at: April 17, 2026, 11:29 p.m.