Triple
T131982
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Appalachian Mountains |
E2672
|
entity |
| Predicate | approximateAge |
P877
|
FINISHED |
| Object | 480 million years |
—
|
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: 480 million years | Statement: [Appalachian Mountains, approximateAge, 480 million years]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approximateAge Context triple: [Appalachian Mountains, approximateAge, 480 million years]
-
A.
hasAge
Indicates that an entity possesses a specific age value, typically expressed as a number of time units since its birth or creation.
-
B.
ageRange
Indicates the span of ages within which an entity or relationship is considered valid or applicable.
-
C.
dateApproximate
chosen
Indicates that the associated date is not exact but estimated or approximate rather than precisely known.
-
D.
approximates
Indicates that one entity is close to, but not exactly equal to, the value, form, or behavior of another entity.
-
E.
servesAgeRange
Indicates that a service, product, or offering is intended for or applicable to entities within a specified age range.
- 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_69a2520c0f3481908b0ed054a2fca8d0 |
completed | Feb. 28, 2026, 2:25 a.m. |
| NER | Named-entity recognition | batch_69a25855baf48190a1b63f2e5865d957 |
completed | Feb. 28, 2026, 2:52 a.m. |
| PD | Predicate disambiguation | batch_69a2564edb488190974dc00eb9ac37d9 |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:30 a.m.