Triple
T19090240
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Laura Roslin |
E467262
|
entity |
| Predicate | elevatedToOfficeBy |
P110758
|
FINISHED |
| Object | line of succession after Cylon attack |
—
|
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: line of succession after Cylon attack | Statement: [Laura Roslin, elevatedToOfficeBy, line of succession after Cylon attack]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: elevatedToOfficeBy Context triple: [Laura Roslin, elevatedToOfficeBy, line of succession after Cylon attack]
-
A.
elevatedTo
Indicates that one entity is promoted or raised to a higher rank, status, position, or level relative to another.
-
B.
wasElevatedTo
chosen
Indicates that an entity was promoted or raised to a higher rank, status, or position.
-
C.
ascendedTo
Indicates that one entity rose, climbed, or moved upward to reach the position, level, or location of another entity.
-
D.
elevatedToDistrictOf
Indicates that an entity has been officially upgraded in status or administrative level to become a district of another entity.
-
E.
builtUnderOfficeOf
Indicates that something was constructed under the authority, supervision, or jurisdiction of a particular office or official body.
- 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_69d8dd05ac4c8190b1967d8f97f3fb2f |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5e34a589c8190b5171fab45bf2204 |
completed | April 20, 2026, 8:26 a.m. |
| PD | Predicate disambiguation | batch_69e4b9a604308190a3235184f9f2c056 |
completed | April 19, 2026, 11:16 a.m. |
Created at: April 10, 2026, 12:04 p.m.