Triple
T22716830
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Counter-Earth |
E561755
|
entity |
| Predicate | hasConceptOriginPeriod |
P38044
|
FINISHED |
| Object | 5th century BCE |
—
|
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: 5th century BCE | Statement: [Counter-Earth, hasConceptOriginPeriod, 5th century BCE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasConceptOriginPeriod Context triple: [Counter-Earth, hasConceptOriginPeriod, 5th century BCE]
-
A.
timePeriodOrigin
chosen
Indicates that one entity is the time period in which the other entity originated or first came into existence.
-
B.
hasConceptualOrigin
Indicates that something conceptually originates from, is derived from, or is fundamentally based on another thing.
-
C.
refersToPeriod
Indicates that one entity designates, references, or is associated with a specific time period or interval.
-
D.
hasConceptOfTime
Indicates that an entity possesses an understanding or awareness of time as an abstract concept or measurable dimension.
-
E.
hasHistoricalOriginInYear
Indicates that something first originated, began, or came into existence in a specified calendar year.
- 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_69e2454fc984819088213b58ee87a002 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1790e14c88190af6acb27910ae9c1 |
completed | April 29, 2026, 3:20 a.m. |
| PD | Predicate disambiguation | batch_69ee62bd657c81909f7b01245b080a5f |
completed | April 26, 2026, 7:08 p.m. |
Created at: April 17, 2026, 3:19 p.m.