Triple
T30193103
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coruscant |
E767546
|
entity |
| Predicate | standardNameInUniverse |
P171472
|
FINISHED |
| Object | Galactic City |
—
|
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: Galactic City | Statement: [Coruscant, standardNameInUniverse, Galactic City]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: standardNameInUniverse Context triple: [Coruscant, standardNameInUniverse, Galactic City]
-
A.
globalStandardName
Indicates that an entity is associated with a standardized name recognized or used globally.
-
B.
universeName
Indicates the name or designated title assigned to a particular universe or cosmic setting.
-
C.
namedAfterInUniverse
Indicates that one entity is, within the fictional or narrative universe, explicitly stated or implied to be named after another entity.
-
D.
inUniverseDesignation
chosen
Indicates that an entity’s name or label is the one used within the fictional universe itself, as opposed to an external or real-world designation.
-
E.
commonNameOf
Indicates that one entity is the commonly used or popular name by which the other entity is known.
- 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_69f2247db1108190835c0727c97637c3 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f7465687bc8190a9da44d62b634ed7 |
completed | May 3, 2026, 12:57 p.m. |
| PD | Predicate disambiguation | batch_69f743f4ceb08190a21fe7f4a99b166b |
completed | May 3, 2026, 12:47 p.m. |
Created at: April 29, 2026, 7:29 p.m.