Triple
T18881888
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AH Reed Memorial Park |
E461847
|
entity |
| Predicate | hasTreeSpeciesCommonName |
P77570
|
FINISHED |
| Object | kauri |
—
|
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: kauri | Statement: [AH Reed Memorial Park, hasTreeSpeciesCommonName, kauri]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTreeSpeciesCommonName Context triple: [AH Reed Memorial Park, hasTreeSpeciesCommonName, kauri]
-
A.
hasScientificNameOfDominantTree
Indicates the scientific (Latin) name of the tree species that is dominant in a given area or context.
-
B.
dominantTreeCommonName
Indicates the common (non-scientific) name of the tree species that is dominant in a given area or ecological context.
-
C.
notableTreeSpecies
Indicates that the subject place or area is known for, or characterized by, the specified tree species.
-
D.
includesSpeciesCommonName
chosen
Indicates that an entity contains or specifies the common (vernacular) name of a species.
-
E.
hasSurroundingTreeCommonName
Indicates that an entity is associated with a surrounding tree identified by its common (vernacular) name.
- 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_69d8dcfc3430819095ee6fc0eb4c06a5 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5c3d2028481908af2b1560312e26c |
completed | April 20, 2026, 6:12 a.m. |
| PD | Predicate disambiguation | batch_69e4a2e27e1481908a8da10b28f07875 |
completed | April 19, 2026, 9:39 a.m. |
Created at: April 10, 2026, 11:57 a.m.