Triple
T38181580
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ngāuruhoe |
E1005179
|
entity |
| Predicate | honouredByToponym |
P81234
|
FINISHED |
| Object | Mount Ngauruhoe |
—
|
NE NERFINISHED |
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: Mount Ngauruhoe | Statement: [Ngāuruhoe, honouredByToponym, Mount Ngauruhoe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: honouredByToponym Context triple: [Ngāuruhoe, honouredByToponym, Mount Ngauruhoe]
-
A.
toponymHonors
chosen
Indicates that a place name is given in honor of, or commemorates, a particular person, group, or entity.
-
B.
legacyToponym
Indicates that one place name is an older or former name historically used to refer to the same geographic entity as another place name.
-
C.
hasToponymicMotivation
Indicates that something is motivated, derived, or named based on a place name (toponym).
-
D.
fieldNamedInHonorOf
Indicates that a field (such as a sports or academic field) bears a particular name as a tribute or dedication to a specific person or entity.
-
E.
inspiredToponymCountry
Indicates that a country’s name was inspired by, derived from, or otherwise based on a particular toponym (place 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_69f76dbc22c481908139b694ffde7a0c |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fcc42cbac48190b8d3e4c9ce140838 |
completed | May 7, 2026, 4:56 p.m. |
| PD | Predicate disambiguation | batch_69fcb0fc69c88190800453eb57a7e62c |
completed | May 7, 2026, 3:34 p.m. |
Created at: May 3, 2026, 4:29 p.m.