Triple
T36792076
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Te Kore |
E909080
|
entity |
| Predicate | relatedRealm |
P68775
|
FINISHED |
| Object | Te Pō |
E1172477
|
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: Te Pō | Statement: [Te Kore, relatedRealm, Te Pō]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedRealm Context triple: [Te Kore, relatedRealm, Te Pō]
-
A.
associatedWithRealm
Indicates a relationship where an entity is linked or connected to a particular realm, domain, or sphere of influence.
-
B.
realmAssociatedWith
chosen
Indicates an association or connection between an entity and a particular realm, domain, or sphere with which it is linked or to which it pertains.
-
C.
realmTypeConnected
Indicates that two realm types are linked or associated in a way that allows interaction, transition, or shared properties between them.
-
D.
includesRealm
Indicates that one entity encompasses or contains a particular realm as part of its scope or domain.
-
E.
realmAlsoCalled
Indicates that a realm is known or referred to by an alternative name or alias.
- 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_69f76e7a937c81909ed7359641e670f6 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3dde5984608190879d32c2bcd1c709 |
completed | June 26, 2026, 2:05 a.m. |
| PD | Predicate disambiguation | batch_6a037a0e039481908a4a2666f76c5363 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:12 p.m.