Triple
T32298144
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mataatua |
E825158
|
entity |
| Predicate | associatedMeetingHouseLocation |
P12391
|
FINISHED |
| Object | Whakatāne |
E410860
|
NE 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: Whakatāne | Statement: [Mataatua, associatedMeetingHouseLocation, Whakatāne]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedMeetingHouseLocation Context triple: [Mataatua, associatedMeetingHouseLocation, Whakatāne]
-
A.
associatedHouse
Indicates a relationship where one entity is linked or connected to a particular house, typically as its related or corresponding house.
-
B.
traditionalMeetingPlace
chosen
Indicates that a location is customarily used as a gathering spot for meetings or social interactions according to established tradition.
-
C.
meetingPlaceOf
Indicates the location where a particular meeting or gathering takes place or is held for the referenced entities.
-
D.
associatedMeeting
Indicates a relationship where one entity is linked or connected to a particular meeting, typically as the meeting that is relevant or related to it.
-
E.
hasMeetingLocation
Indicates that an entity (such as a meeting or event) takes place at or is associated with a specific location.
- F. None of above.
Provenance (4 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_69f349115304819084ee91d345b6c8aa |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a346661ffd4819085f512c7bdf70c39 |
completed | June 18, 2026, 9:42 p.m. |
| PD | Predicate disambiguation | batch_6a0379edf2d88190b492fca86ed23cac |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 12:44 a.m.