Triple
T21492311
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Takahanga Marae |
E530266
|
entity |
| Predicate | hasMeetingHouseNameOrigin |
P3325
|
FINISHED |
| Object | named after ancestor Maru Kaitātea |
—
|
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: named after ancestor Maru Kaitātea | Statement: [Takahanga Marae, hasMeetingHouseNameOrigin, named after ancestor Maru Kaitātea]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMeetingHouseNameOrigin Context triple: [Takahanga Marae, hasMeetingHouseNameOrigin, named after ancestor Maru Kaitātea]
-
A.
hasNameOrigin
chosen
Indicates that the origin or source of an entity’s name is specified by the related entity.
-
B.
clanNameOrigin
Indicates the source or basis from which a clan’s name is derived.
-
C.
possibleNameEtymology
Indicates a hypothesized or suggested origin or derivation of an entity’s name from another term, source, or linguistic root.
-
D.
hasNameEtymologyIn
Indicates that the origin or derivation of an entity’s name is based in, or traceable to, a specified source such as a language, place, or cultural context.
-
E.
districtNameOrigin
Indicates that the relationship specifies the origin or source from which a district’s name is derived.
- 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_69e0c45bd15481909fba5910765cdda2 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69e9ea3ba2fc81909638bbb3e1d92ea5 |
completed | April 23, 2026, 9:45 a.m. |
| PD | Predicate disambiguation | batch_69e631f6e68081908f5ee4ce7413803e |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:23 p.m.