Triple
T31421683
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Evolver universe |
E801546
|
entity |
| Predicate | hasPrimaryLocaleOfActionFor |
P202240
|
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, hasPrimaryLocaleOfActionFor, Starlight]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrimaryLocaleOfActionFor Context triple: [Evolver universe, hasPrimaryLocaleOfActionFor, Starlight]
-
A.
hasMainLocale
Indicates that an entity’s primary or default locale (language and regional setting) is a specified locale.
-
B.
hasPrimaryLanguage1
Indicates that an entity’s main or most commonly used language is the specified language.
-
C.
hasPrimaryLanguageBranch
Indicates that an entity’s main or dominant language belongs to a specified language branch or family.
-
D.
hasPrimaryVernacularLanguageFamily
Indicates that an entity’s main vernacular language belongs to a specified language family.
-
E.
hasPrimaryLanguageNearby
Indicates that an entity is associated with a primary language that is predominantly used or present in its immediate geographic or contextual vicinity.
- 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_69f348c26f048190b4adadd71b4596c5 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_6a0064f8efa48190956287f548a8057d |
completed | May 10, 2026, 10:59 a.m. |
| PD | Predicate disambiguation | batch_6a006471e75c8190adae99bd75e7411b |
completed | May 10, 2026, 10:56 a.m. |
| PDg | Predicate description generation | batch_6a0064f8496081908ac3bb4c53ed08aa |
completed | May 10, 2026, 10:59 a.m. |
Created at: April 30, 2026, 8:48 p.m.