Triple
T23430150
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Los Alerces National Park |
E563303
|
entity |
| Predicate | mainTreeSpeciesCommonName |
P80238
|
FINISHED |
| Object | alerce |
—
|
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: alerce | Statement: [Los Alerces National Park, mainTreeSpeciesCommonName, alerce]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainTreeSpeciesCommonName Context triple: [Los Alerces National Park, mainTreeSpeciesCommonName, alerce]
-
A.
notableTreeSpecies
Indicates that the subject place or area is known for, or characterized by, the specified tree species.
-
B.
hasScientificNameOfDominantTree
Indicates the scientific (Latin) name of the tree species that is dominant in a given area or context.
-
C.
dominantTreeCommonName
chosen
Indicates the common (non-scientific) name of the tree species that is dominant in a given area or ecological context.
-
D.
commonTreeType
Indicates that two or more entities share the same type or classification of tree.
-
E.
treeHabit
Indicates the growth form or structural habit characteristic of a tree, such as its typical shape, branching pattern, or overall stature.
- 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_69e24553980c8190bb66a2ae0bdab125 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f1a5d6d1c881908e3c4ac0e7cd30cd |
completed | April 29, 2026, 6:31 a.m. |
| PD | Predicate disambiguation | batch_69f061f92da081908e7f1d0cd1e9b01c |
completed | April 28, 2026, 7:30 a.m. |
Created at: April 17, 2026, 5:48 p.m.