Triple
T36017945
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USS Enterprise-G |
E1041897
|
entity |
| Predicate | predecessorInName |
P195744
|
FINISHED |
| Object | USS Enterprise-F |
—
|
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-F | Statement: [USS Enterprise-G, predecessorInName, USS Enterprise-F]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: predecessorInName Context triple: [USS Enterprise-G, predecessorInName, USS Enterprise-F]
-
A.
predecessorName
Indicates that the value is the name of an entity that directly precedes another in an ordered sequence or lineage.
-
B.
predecessorNameForm
Indicates that the value is a name or naming form previously used for the same entity before its current name.
-
C.
predecessorNameUsage
Indicates that a name was used previously and has been replaced or superseded by a subsequent name in a sequence or lineage.
-
D.
predecessorRealName
Indicates that one entity is the real (actual) name of the predecessor of another entity.
-
E.
shortNameOfPredecessor
Indicates that an entity has a predecessor whose abbreviated or shorter name is being specified.
- 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_69f76e2b981881908e4e160607fa82eb |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fde49a084081909d99b1e0258169d5 |
completed | May 8, 2026, 1:26 p.m. |
| PD | Predicate disambiguation | batch_69fde1d04bd881909a46ecbbf18dfe59 |
completed | May 8, 2026, 1:14 p.m. |
| PDg | Predicate description generation | batch_69fde49953c481909ac352ab36fa9ff2 |
completed | May 8, 2026, 1:26 p.m. |
Created at: May 3, 2026, 4:07 p.m.