Triple
T16952800
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Founders Grove |
E411223
|
entity |
| Predicate | hasTreeAgeRange |
P122542
|
FINISHED |
| Object | several hundred 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: several hundred years | Statement: [Founders Grove, hasTreeAgeRange, several hundred years]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTreeAgeRange Context triple: [Founders Grove, hasTreeAgeRange, several hundred years]
-
A.
standAge
Indicates the age or time duration that a particular stand (e.g., a forest stand or grouped vegetation area) has existed or been established.
-
B.
hasApproximateAgeRange
chosen
Indicates that one entity is associated with another entity representing an estimated or non-exact span of ages.
-
C.
containsAge
Indicates that one entity includes or specifies the age value or age-related information of another entity.
-
D.
treeLongevity
Indicates the duration or lifespan of a tree, typically measured from planting or germination to death or removal.
-
E.
hasTreeVigor
Indicates the assessed strength, health, and growth potential of a tree in relation to its current condition or environment.
- 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_69d886c9c9d481909afe222093641cae |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3d01a4ae8819085a6ce01fbc71b0f |
completed | April 18, 2026, 6:40 p.m. |
| PD | Predicate disambiguation | batch_69e32b9aa8748190b248890aca86753d |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:31 a.m.