Triple
T31421692
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Evolver universe |
E801546
|
entity |
| Predicate | hasCanonicalStatusFor |
P33854
|
FINISHED |
| Object | Starlight |
—
|
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: Starlight | Statement: [Evolver universe, hasCanonicalStatusFor, Starlight]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCanonicalStatusFor Context triple: [Evolver universe, hasCanonicalStatusFor, Starlight]
-
A.
hasPartInCanonizationStatus
Indicates that an entity participates in or contributes to determining another entity’s canonization status.
-
B.
canonicalStatus
Indicates the formal or official standing of an entity within an established authoritative or normative system.
-
C.
canonicalStatusIn
chosen
Indicates that something has a particular canonical or officially recognized status within a specified context or system.
-
D.
isCanonicalOn
Indicates that something is recognized as the standard or authoritative form of another entity within a given context.
-
E.
hasCanonicalStatusInGenre
Indicates that an entity holds a widely recognized, authoritative, or classic status within a particular genre.
- 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_69f348c26f048190b4adadd71b4596c5 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fe7bfc94bc81909eeec946e8c1c450 |
completed | May 9, 2026, 12:12 a.m. |
| PD | Predicate disambiguation | batch_69fe7b74a1188190886f128e07f712da |
completed | May 9, 2026, 12:10 a.m. |
Created at: April 30, 2026, 8:49 p.m.