Triple
T32111109
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kaikohekohe |
E820118
|
entity |
| Predicate | isInPartOfCountry |
P45703
|
FINISHED |
| Object | Far North of New Zealand |
—
|
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: Far North of New Zealand | Statement: [Kaikohekohe, isInPartOfCountry, Far North of New Zealand]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isInPartOfCountry Context triple: [Kaikohekohe, isInPartOfCountry, Far North of New Zealand]
-
A.
hasPartInCountry
Indicates that an entity has a component, section, or portion that is located within a specified country.
-
B.
existsInConstituentCountry
Indicates that one entity is located within or is present in a country that is a constituent part of a larger sovereign state.
-
C.
isInGeopoliticalEntity
chosen
Indicates that one entity is located within, or is a part of, a specific geopolitical unit such as a country, state, or city.
-
D.
meetsInCountry
Indicates that two or more entities have an in-person meeting that takes place within the specified country.
-
E.
alsoInCountry
Indicates that something located in one country is additionally located or present in another specified country.
- 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_69f3490209c881908ec0241476715f15 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b69f49d881909de19dec9c5459c5 |
completed | May 3, 2026, 2:44 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a970b0819090c6473844ffa8e3 |
completed | May 3, 2026, 2:32 a.m. |
Created at: May 1, 2026, 12:27 a.m.