Triple
T475815
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tongariro National Park |
E9057
|
entity |
| Predicate | isRecognizedFor |
P753
|
FINISHED |
| Object | active volcanoes |
—
|
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: active volcanoes | Statement: [Tongariro National Park, isRecognizedFor, active volcanoes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isRecognizedFor Context triple: [Tongariro National Park, isRecognizedFor, active volcanoes]
-
A.
recognizedFor
chosen
Indicates that one entity is acknowledged, credited, or honored for a particular achievement, quality, contribution, or work associated with another entity.
-
B.
recognizedIn
Indicates that an entity is formally acknowledged, honored, or given recognition within a particular context, setting, or domain.
-
C.
recognizedAs
Indicates that one entity is acknowledged or accepted as having the identity, role, status, or classification of another entity.
-
D.
formOfRecognition
Indicates a relationship where one entity serves as an official acknowledgment, honor, or validation granted to another entity.
-
E.
recognizedRight
Indicates that an agent formally acknowledges and accepts that another party possesses a specific right or entitlement.
- 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_69a2e7ff81708190b0507a24a997232c |
completed | Feb. 28, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69a2f03b5e5081908ee3dba9d19a6871 |
completed | Feb. 28, 2026, 1:40 p.m. |
| PD | Predicate disambiguation | batch_69a2edeed31881908cf43beed410572d |
completed | Feb. 28, 2026, 1:30 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.