Triple
T29074725
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Korellian Republic |
E735905
|
entity |
| Predicate | timePeriodWithinUniverse |
P6261
|
FINISHED |
| Object | early centuries of 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: early centuries of the Foundation Era | Statement: [The Korellian Republic, timePeriodWithinUniverse, early centuries of the Foundation Era]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timePeriodWithinUniverse Context triple: [The Korellian Republic, timePeriodWithinUniverse, early centuries of the Foundation Era]
-
A.
timePeriodWithin
chosen
Indicates that one time period is entirely contained within the bounds of another time period.
-
B.
timePeriod
Indicates the specific span or interval of time during which an event, state, or relationship occurs or is valid.
-
C.
timePeriodFormulated
Indicates the time period during which something (such as a concept, theory, or plan) was formulated or developed.
-
D.
timeInUniverseEnds
Indicates that the duration or existence of the universe comes to a final end at a specified time or event.
-
E.
timePeriodAnalyzed
Indicates that a specified time period is the focus or scope of an analysis or evaluation.
- 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_69f077e9b0a48190bb79548279cb7f64 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f6bbf6e33c819086e5176d64e7a614 |
completed | May 3, 2026, 3:07 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6b1e6c8190adf9d6a257e0b744 |
completed | May 3, 2026, 3 a.m. |
Created at: April 28, 2026, 10:22 a.m.