Triple
T2000502
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Archean Eon |
E43458
|
entity |
| Predicate | startTimeLowerBound |
P288
|
FINISHED |
| Object | about 4,000 million years ago |
—
|
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: about 4,000 million years ago | Statement: [Archean Eon, startTimeLowerBound, about 4,000 million years ago]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startTimeLowerBound Context triple: [Archean Eon, startTimeLowerBound, about 4,000 million years ago]
-
A.
startTimeAsRepresentative
Indicates the time at which an entity begins serving or acting in a representative capacity.
-
B.
startDate
chosen
Indicates the point in time when an event, state, or relationship begins.
-
C.
startsAt
Indicates that an event, process, or state begins at a specific time, location, or point in a sequence.
-
D.
lowerLimit
Indicates that one value serves as the minimum or smallest allowable bound or threshold for another value or range.
-
E.
typicalStartPeriod
Indicates the usual or standard time period during which something begins or is initiated.
- 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_69a88715dbbc8190b2299e29e955d997 |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abb87f78f0819098e787a5f3e062fd |
completed | March 7, 2026, 5:32 a.m. |
| PD | Predicate disambiguation | batch_69abb79e63c08190982c8b44a557266f |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:37 p.m.