Triple
T9304003
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grenville orogenic belt |
E223835
|
entity |
| Predicate | ageDescription |
P61009
|
FINISHED |
| Object | over one billion years old |
—
|
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: over one billion years old | Statement: [Grenville orogenic belt, ageDescription, over one billion years old]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ageDescription Context triple: [Grenville orogenic belt, ageDescription, over one billion years old]
-
A.
ageDetail
chosen
Indicates a detailed specification of an entity’s age, such as exact value, range, or related age attributes.
-
B.
ageRange
Indicates the span of ages within which an entity or relationship is considered valid or applicable.
-
C.
ageBased
Indicates a relationship or condition that depends on or is determined by the age of the entities involved.
-
D.
ageStatus
Indicates the relationship between an entity and its classification into an age-related category or status (e.g., minor, adult, senior).
-
E.
ageGroup
Indicates the categorical age range or bracket to which an entity belongs.
- 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_69ca8424d0f08190831e2e93c6533aeb |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd1da623ac81908bab6dfb1bbce25d |
completed | April 1, 2026, 1:29 p.m. |
| PD | Predicate disambiguation | batch_69cc7a5ef1908190bc5ca166bb895af6 |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:36 p.m.