Triple
T33839590
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Imbrian period |
E867322
|
entity |
| Predicate | hasApproximateEndAge |
P193559
|
FINISHED |
| Object | 3.2 billion 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: 3.2 billion years ago | Statement: [Imbrian period, hasApproximateEndAge, 3.2 billion years ago]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasApproximateEndAge Context triple: [Imbrian period, hasApproximateEndAge, 3.2 billion years ago]
-
A.
hasApproximateUpperAge
Indicates that an entity is associated with an estimated or non-exact maximum age limit.
-
B.
hasApproximateAgeRange
Indicates that one entity is associated with another entity representing an estimated or non-exact span of ages.
-
C.
approximateStartAge
Indicates the estimated or roughly determined age at which an event, condition, or state begins.
-
D.
endAgeMa
Indicates the age (in years) at which a marriage or marital relationship ends.
-
E.
hasRelativeAge
Indicates that one entity has an age that is defined or compared in relation to the age of another entity.
- F. None of above. chosen
Provenance (4 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_69f34992ad40819087760ed939bd2a7a |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fd49f6dbac81909744373a357b7982 |
completed | May 8, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69fd48ed68f481908374183c66a6b055 |
completed | May 8, 2026, 2:22 a.m. |
| PDg | Predicate description generation | batch_69fd49f612a4819096fe7d5a3bb439ba |
completed | May 8, 2026, 2:27 a.m. |
Created at: May 1, 2026, 1:47 a.m.