Triple
T8492826
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Solaria |
E201013
|
entity |
| Predicate | laterChronologicalPlacement |
P6880
|
FINISHED |
| Object | revisited thousands of years later in the Foundation era |
—
|
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: revisited thousands of years later in the Foundation era | Statement: [Solaria, laterChronologicalPlacement, revisited thousands of years later in the Foundation era]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterChronologicalPlacement Context triple: [Solaria, laterChronologicalPlacement, revisited thousands of years later in the Foundation era]
-
A.
chronologicallyAfter
chosen
Indicates that one event or state occurs later in time than another.
-
B.
chronologicalPosition
Indicates the relative ordering of one event or entity in time with respect to another.
-
C.
locatedAfter
Indicates that one entity is positioned later than another along a defined sequence, order, or spatial/temporal axis.
-
D.
laterReleased
Indicates that one entity was released at a time chronologically after the release of another entity.
-
E.
laterDeployedIn
Indicates that one entity was deployed or put into operation in a particular context, location, or system at a later time than another.
- 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_69ca831ee390819095fae73400bbfafc |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe55cf5dc81908cad31ac53e15b46 |
completed | March 31, 2026, 3:16 p.m. |
| PD | Predicate disambiguation | batch_69cbd10a4b0881909e254117780dc823 |
completed | March 31, 2026, 1:50 p.m. |
Created at: March 30, 2026, 6:13 p.m.