Triple
T25186702
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NX-01 |
E630736
|
entity |
| Predicate | successorInNaming |
P85144
|
FINISHED |
| Object | USS Enterprise (NCC-1701) |
—
|
NE NERFINISHED |
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: USS Enterprise (NCC-1701) | Statement: [NX-01, successorInNaming, USS Enterprise (NCC-1701)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successorInNaming Context triple: [NX-01, successorInNaming, USS Enterprise (NCC-1701)]
-
A.
namedSuccessor
chosen
Indicates that one entity has been explicitly designated as the successor or heir to another entity.
-
B.
namedAfterSuccessor
Indicates that an entity is named after another entity that succeeds or follows it in time, position, or sequence.
-
C.
successorPrefix
Indicates that one sequence is formed by taking another sequence and replacing its final element with its immediate successor, while keeping all preceding elements identical.
-
D.
successorInLineage
Indicates that one entity is the next direct descendant or inheritor in a genealogical or hierarchical lineage from another entity.
-
E.
successorDeterminedBy
Indicates that the identity of a successor is established or chosen according to a specified rule, process, or determining factor.
- 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_69e75a8a6d088190ba1e82a4345225e7 |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f657f653448190a945b4751af8507d |
completed | May 2, 2026, 8 p.m. |
| PD | Predicate disambiguation | batch_69f6575ba12081909396036f78757a76 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 21, 2026, 12:44 p.m.