Triple
T31421681
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Evolver universe |
E801546
|
entity |
| Predicate | hasContinuityFor |
P66479
|
FINISHED |
| Object | Starlight |
E211656
|
NE 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: Starlight | Statement: [Evolver universe, hasContinuityFor, Starlight]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasContinuityFor Context triple: [Evolver universe, hasContinuityFor, Starlight]
-
A.
hasInternalContinuity
Indicates that something maintains an unbroken, consistent state or structure within itself over time or across its internal parts.
-
B.
belongsToContinuity
chosen
Indicates that something is part of, or exists within, a specific narrative or temporal continuity.
-
C.
continuityOf
Indicates that one entity represents an unbroken continuation, extension, or persistence of another over time or across a process or state.
-
D.
hasRepresentationContinuity
Indicates that one entity maintains a consistent or continuous representational relationship with another across time, context, or state changes.
-
E.
hasContinuo
Indicates that a musical work, section, or passage includes a basso continuo part or accompaniment.
- F. None of above.
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_6a022348ae2881908eae1be79b6f6ff6 |
completed | May 11, 2026, 6:43 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2b07709f988190ab00938539763f34 |
completed | June 11, 2026, 7:07 p.m. |
| PD | Predicate disambiguation | batch_6a0220beb6b08190981fb86363757517 |
completed | May 11, 2026, 6:32 p.m. |
Created at: April 30, 2026, 8:48 p.m.