Triple
T38027625
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Taurahe |
E948820
|
entity |
| Predicate | notableLocationWhereSpoken |
P3858
|
FINISHED |
| Object | Elder Rise |
E944654
|
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: Elder Rise | Statement: [Taurahe, notableLocationWhereSpoken, Elder Rise]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableLocationWhereSpoken Context triple: [Taurahe, notableLocationWhereSpoken, Elder Rise]
-
A.
isSpokenOn
Indicates that a particular language, phrase, or utterance is used or occurs during a specified time, event, or occasion.
-
B.
historicallySpokenIn
Indicates that a language was used for spoken communication in a particular place or region during a past historical period.
-
C.
notableLocation
chosen
Indicates that a location is especially significant, prominent, or noteworthy in relation to the subject.
-
D.
usedForLanguageSpokenIn
Indicates that something (such as a resource, tool, or medium) is used for expressing or communicating a language that is spoken in a particular place or region.
-
E.
notableRoleLocation
Indicates that an entity’s notable role, position, or function is specifically associated with a particular geographic 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_69f76efd1bc48190a729097fe5177b61 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a037df1223c8190a5d61e4f8e6fd613 |
completed | May 12, 2026, 7:22 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a41544131088190a33f57344e2cae5e |
completed | June 28, 2026, 5:05 p.m. |
| PD | Predicate disambiguation | batch_6a037a1ad6c48190bfe35d350c1b4751 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:20 p.m.