Triple
T4864728
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Huachuca Mountains foothills |
E108739
|
entity |
| Predicate | typicalVegetationGenus |
P12304
|
FINISHED |
| Object | Quercus (oak) |
—
|
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: Quercus (oak) | Statement: [Huachuca Mountains foothills, typicalVegetationGenus, Quercus (oak)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalVegetationGenus Context triple: [Huachuca Mountains foothills, typicalVegetationGenus, Quercus (oak)]
-
A.
vegetationType
Indicates the specific kind or category of plant cover or flora that characterizes a given area or environment.
-
B.
vegetation
Indicates that an area or object is covered with, contains, or is characterized by plant life.
-
C.
plantType
Indicates the specific kind or category of plant that an entity is classified as.
-
D.
isPlantOf
Indicates that one entity is a plant that belongs to, is associated with, or is characteristic of another entity (such as a region, habitat, or owner).
-
E.
notableGenus
chosen
Indicates that one entity is a genus that is especially prominent, well-known, or significant in relation to the other entity.
- 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_69bd440b965081908b0557721cae6338 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6d7861e88190ad172632eb5507c7 |
completed | March 20, 2026, 3:53 p.m. |
| PD | Predicate disambiguation | batch_69bd6c27334481909ba8ac80854f7d8e |
completed | March 20, 2026, 3:47 p.m. |
Created at: March 20, 2026, 1:26 p.m.