Triple
T19821343
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NMS Mircea |
E476200
|
entity |
| Predicate | crew includes |
P94498
|
FINISHED |
| Object | naval cadets |
—
|
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: naval cadets | Statement: [NMS Mircea, crew includes, naval cadets]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: crew includes Context triple: [NMS Mircea, crew includes, naval cadets]
-
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.
crewInvolvedIn
Indicates that a crew (as a group or unit) participates in, contributes to, or is otherwise involved in a specified event, activity, or operation.
-
C.
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.
-
D.
crewOnboard
chosen
Indicates that a person or group is serving as crew aboard a specific vehicle, vessel, or craft.
-
E.
featureCrew
Indicates that a particular crew member is highlighted or designated as a featured participant within a crew-related context.
- 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_69d8e51c7c188190b926f3a2a7b5f881 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e654fee3e48190ae728e49748ad268 |
completed | April 20, 2026, 4:31 p.m. |
| PD | Predicate disambiguation | batch_69e5305bda388190a23b7191768107b1 |
completed | April 19, 2026, 7:43 p.m. |
Created at: April 10, 2026, 1:50 p.m.