Triple
T18440017
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ngaruroro River |
E450500
|
entity |
| Predicate | hasUpperReachesCharacter |
P131606
|
FINISHED |
| Object | braided channels |
—
|
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: braided channels | Statement: [Ngaruroro River, hasUpperReachesCharacter, braided channels]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasUpperReachesCharacter Context triple: [Ngaruroro River, hasUpperReachesCharacter, braided channels]
-
A.
hasUppercase
Indicates that an entity contains at least one uppercase (capital) letter.
-
B.
hasUpperPartFrom
Indicates that an entity includes, incorporates, or is composed of an upper part originating from another entity.
-
C.
hasUpperCourseName
Indicates that an entity (such as a course instance or section) is associated with the name of the higher-level or parent course of which it is a part.
-
D.
hasUpperTier
Indicates that one entity occupies a higher or superior level, rank, or layer in a hierarchical structure relative to another entity.
-
E.
hasUpperCave
Indicates that an entity possesses or is associated with an upper cave, typically a cave located above another level or reference point.
- F. None of above. chosen
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_69d8d381d6388190a9e94e9c658174e4 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e51c0fda908190901a108fb9982a2d |
completed | April 19, 2026, 6:16 p.m. |
| PD | Predicate disambiguation | batch_69e469c943a4819094c8fdc5971ad3a7 |
completed | April 19, 2026, 5:36 a.m. |
| PDg | Predicate description generation | batch_69e46d2aa72c8190a40854a7a52081e2 |
completed | April 19, 2026, 5:50 a.m. |
Created at: April 10, 2026, 11:30 a.m.