Triple
T30419047
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rakeahua River |
E773841
|
entity |
| Predicate | hasAssociatedTrack |
P3284
|
FINISHED |
| Object | Rakeahua Track |
—
|
NE NERFINISHED |
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: Rakeahua Track | Statement: [Rakeahua River, hasAssociatedTrack, Rakeahua Track]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAssociatedTrack Context triple: [Rakeahua River, hasAssociatedTrack, Rakeahua Track]
-
A.
hasTrack
chosen
Indicates that one entity possesses, includes, or is associated with a specific track (such as a path, course, or recorded item).
-
B.
associatedWithTrack
Indicates a relationship in which an entity is linked or connected to a specific track, such as being part of, derived from, or relevant to that track.
-
C.
hasTrackContext
Indicates that an entity is associated with or occurs within a particular track-related context (such as a specific track, route, or sequence).
-
D.
containsTrackType
Indicates that one entity includes or is associated with a specific type or category of track.
-
E.
hasTrackSection
Indicates that an entity includes, is composed of, or is associated with a specific section or segment of a track.
- 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_69f22491ba248190b9a4776ca8e42d02 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f71422adac8190a5ceb32dcf820833 |
completed | May 3, 2026, 9:23 a.m. |
| PD | Predicate disambiguation | batch_69f712764d2c819081b64b27e5de4a13 |
completed | May 3, 2026, 9:16 a.m. |
Created at: April 29, 2026, 8:05 p.m.