Triple
T21581116
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ultima |
E532524
|
entity |
| Predicate | previousSystemNickname |
P65
|
FINISHED |
| Object | 2014 MU69 |
—
|
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: 2014 MU69 | Statement: [Ultima, previousSystemNickname, 2014 MU69]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previousSystemNickname Context triple: [Ultima, previousSystemNickname, 2014 MU69]
-
A.
formerName
chosen
Indicates that an entity was previously known by a different name in the past.
-
B.
predecessorSystem
Indicates that one system existed or was in use before and was replaced or superseded by another system.
-
C.
previousNameUsedUntil
Indicates that a particular name was used for an entity up to (but not necessarily including) a specified end date or time.
-
D.
predecessorSystemType
Indicates that one system type functioned as the predecessor or earlier version to another system type.
-
E.
formerlyKnownLocationAs
Indicates that an entity was previously known or referred to by a different location name or designation.
- 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_69e0c4618bec8190bcb0feb74568cbb1 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69eeeb5c496c819093113dd5790fca48 |
completed | April 27, 2026, 4:51 a.m. |
| PD | Predicate disambiguation | batch_69e6320c8c2c81908bf031447d66a052 |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:31 p.m.