Triple
T22175512
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USS Enterprise (NCC-1701-E) |
E548038
|
entity |
| Predicate | commandCrew |
P147261
|
FINISHED |
| Object | The Next Generation crew |
—
|
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: The Next Generation crew | Statement: [USS Enterprise (NCC-1701-E), commandCrew, The Next Generation crew]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commandCrew Context triple: [USS Enterprise (NCC-1701-E), commandCrew, The Next Generation crew]
-
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
Indicates that a person or group is serving as crew aboard a specific vehicle, vessel, or craft.
-
C.
commanderOnBoard
Indicates that a specific individual holds the role of commanding officer on a particular vehicle, vessel, or craft during its operation.
-
D.
crewSystem
Indicates a relationship where a system is specifically designed for, assigned to, or operated by a particular crew.
-
E.
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.
- 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_69e11e3d53f88190a2b690e3f25bb062 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f12a6b755c81909e9bd2a588c065b3 |
completed | April 28, 2026, 9:45 p.m. |
| PD | Predicate disambiguation | batch_69e71b41555881909b8e22718974d527 |
completed | April 21, 2026, 6:37 a.m. |
| PDg | Predicate description generation | batch_69e7222d208c819098b12c13e31af629 |
completed | April 21, 2026, 7:07 a.m. |
Created at: April 16, 2026, 8:34 p.m.