Triple
T34969067
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Resolutions |
E1008483
|
entity |
| Predicate | firstOfficerStrandedOnPlanet |
P44545
|
FINISHED |
| Object | Chakotay |
E308616
|
NE 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: Chakotay | Statement: [Resolutions, firstOfficerStrandedOnPlanet, Chakotay]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstOfficerStrandedOnPlanet Context triple: [Resolutions, firstOfficerStrandedOnPlanet, Chakotay]
-
A.
firstOfficer
chosen
Indicates that one entity serves as the first officer (second-in-command) to another entity, typically in a hierarchical or command structure.
-
B.
firstOfficerSpecies
Indicates that the specified species is the species to which the first officer of a given crew, vessel, or organization belongs.
-
C.
firstCrewMember
Indicates that the subject is the first (earliest or primary) member within a specified crew or group.
-
D.
firstMissionCommander
Indicates that the subject served as the commander of the object's first mission.
-
E.
firstRendezvousMission
Indicates that the mission is the first instance in which two or more entities conduct a rendezvous operation.
- F. None of above.
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_69f76dc78a308190a1ac29ad4a9a4895 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3885d2ecdc81909ae0f3af6d600799 |
completed | June 22, 2026, 12:46 a.m. |
| PD | Predicate disambiguation | batch_6a0379ff1ba081908eda86acefcf69fb |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4 p.m.