Triple
T29548566
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Notron |
E749695
|
entity |
| Predicate | galacticRole |
P22653
|
FINISHED |
| Object | capital world precursor |
—
|
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: capital world precursor | Statement: [Notron, galacticRole, capital world precursor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: galacticRole Context triple: [Notron, galacticRole, capital world precursor]
-
A.
roleInGalaxy
chosen
Indicates the specific function, status, or influence an entity holds within the broader structure or dynamics of a galaxy.
-
B.
galacticImportance
Indicates the degree to which something holds significant influence, relevance, or priority at a galactic scale.
-
C.
galacticAffiliation
Indicates the larger galactic group, faction, or polity with which an entity is formally associated or aligned.
-
D.
galacticComponent
Indicates that one entity is a structural part or subregion of a galaxy, such as a disk, bulge, halo, or similar galactic subdivision.
-
E.
roleInNebula
Indicates that an entity holds a specific function, position, or involvement within a particular nebula.
- 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_69f0bd48691081908cecad39bac591e0 |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69f66cf549788190a0084c5de634fd68 |
completed | May 2, 2026, 9:30 p.m. |
| PD | Predicate disambiguation | batch_69f6633ac8a88190ab0cda62bbfcf9b0 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 28, 2026, 5:10 p.m.