Triple
T36017967
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USS Enterprise-G |
E1041897
|
entity |
| Predicate | designationChangeFrom |
P199276
|
FINISHED |
| Object | USS Titan-A |
—
|
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 Titan-A | Statement: [USS Enterprise-G, designationChangeFrom, USS Titan-A]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designationChangeFrom Context triple: [USS Enterprise-G, designationChangeFrom, USS Titan-A]
-
A.
changedProfessionalNameFrom
Indicates that an entity has altered its professional or working name from a specified previous name.
-
B.
changedFrom
Indicates that an entity previously had one state, value, or form and was altered or updated from that prior condition to a new one.
-
C.
roleReplacedOn
Indicates that one role has been substituted or taken over by another role at a specific point in time.
-
D.
namespaceChangedFrom
Indicates that an entity’s namespace has been modified, specifying the previous namespace it was changed from.
-
E.
changedUnder
Indicates that one entity has undergone alteration, modification, or transformation as a result of the influence, action, or conditions imposed by another entity.
- 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_69ff29d831b881908d485609e0fc1d0b |
completed | May 9, 2026, 12:34 p.m. |
| PD | Predicate disambiguation | batch_69ff28f9f9e4819087f3402735de66c7 |
completed | May 9, 2026, 12:30 p.m. |
| PDg | Predicate description generation | batch_69ff29d77f48819085304ed5e92eb906 |
completed | May 9, 2026, 12:34 p.m. |
Created at: May 3, 2026, 4:07 p.m.