Triple
T5214336
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Christopher Pike |
E117711
|
entity |
| Predicate | captaincyPrecedes |
P62075
|
FINISHED |
| Object | James T. Kirk’s command of the Enterprise |
—
|
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: James T. Kirk’s command of the Enterprise | Statement: [Christopher Pike, captaincyPrecedes, James T. Kirk’s command of the Enterprise]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: captaincyPrecedes Context triple: [Christopher Pike, captaincyPrecedes, James T. Kirk’s command of the Enterprise]
-
A.
captaincyStartYear
Indicates the year in which an entity first assumed the role of captain.
-
B.
captaincyFormat
Indicates the specific structure or style in which a captaincy role or tenure is represented or recorded.
-
C.
captain
Indicates that one entity serves as the leader or person in command of another entity, typically a team, group, or vessel.
-
D.
captaincyEndYear
Indicates the year in which an entity’s period of serving as captain comes to an end.
-
E.
captainPosition
Indicates that an entity holds the role or position of captain in relation to another entity (such as a team, vessel, or group).
- 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_69bd4464ba3c8190bc16b2ebbe42ddb0 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd7a911d40819086621537274dc0f0 |
completed | March 20, 2026, 4:49 p.m. |
| PD | Predicate disambiguation | batch_69bd77bb4e8c819094b5ac7cf61512f9 |
completed | March 20, 2026, 4:37 p.m. |
| PDg | Predicate description generation | batch_69bd79000cf88190b3c05d95395b0cd2 |
completed | March 20, 2026, 4:42 p.m. |
Created at: March 20, 2026, 1:47 p.m.