Triple
T32438997
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kurahaupō |
E828959
|
entity |
| Predicate | hasDescendantGroups |
P47820
|
FINISHED |
| Object | iwi of Kurahaupō waka |
—
|
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: iwi of Kurahaupō waka | Statement: [Kurahaupō, hasDescendantGroups, iwi of Kurahaupō waka]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDescendantGroups Context triple: [Kurahaupō, hasDescendantGroups, iwi of Kurahaupō waka]
-
A.
haveSubgroups
chosen
Indicates that an entity is organized into smaller constituent groups that are part of it.
-
B.
hasSubgroupStatus
Indicates that one group holds a specific status or classification as a subgroup within a larger group or organization.
-
C.
hasDescendantCommunitiesIn
Indicates that a community has descendant or subordinate communities located within a specified place or region.
-
D.
hasDescendantsRegion
Indicates that an entity has descendants or subordinate elements that are located within, originate from, or are associated with a specified region.
-
E.
containsGroup
Indicates that one entity includes or encompasses a specific group of entities within it.
- 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_69f3491bf298819097b610f772d54a6d |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fea5e828cc8190a9b755a645dc56d2 |
completed | May 9, 2026, 3:11 a.m. |
| PD | Predicate disambiguation | batch_69fea36443f08190b2aced9b4a0525fd |
completed | May 9, 2026, 3 a.m. |
Created at: May 1, 2026, 12:55 a.m.