Triple
T16952802
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Founders Grove |
E411223
|
entity |
| Predicate | hasTreeHeightRange |
P1342
|
FINISHED |
| Object | over 300 feet (for some trees) |
—
|
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 300 feet (for some trees) | Statement: [Founders Grove, hasTreeHeightRange, over 300 feet (for some trees)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTreeHeightRange Context triple: [Founders Grove, hasTreeHeightRange, over 300 feet (for some trees)]
-
A.
hasHeight
Indicates that one entity possesses a specific vertical measurement or stature.
-
B.
hasTree
Indicates that one entity possesses, contains, or is associated with a tree.
-
C.
plantHeight
chosen
Indicates the measured vertical size or growth extent of a plant from its base to its top.
-
D.
hasSignificantHeight
Indicates that one entity’s height is notably large or substantial relative to a given standard or to other entities.
-
E.
shoulderHeightRange
Indicates the range of vertical height measured from the ground to an entity’s shoulders.
- 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.