Triple
T25982597
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Freshwater–Mason Bay track |
E646107
|
entity |
| Predicate | hasAssociatedHut |
P163041
|
FINISHED |
| Object | Freshwater Hut |
—
|
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: Freshwater Hut | Statement: [Freshwater–Mason Bay track, hasAssociatedHut, Freshwater Hut]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAssociatedHut Context triple: [Freshwater–Mason Bay track, hasAssociatedHut, Freshwater Hut]
-
A.
hasHutNetwork
Indicates that an entity possesses or is associated with a connected system or network of huts.
-
B.
hasHistoricHut
Indicates that an entity possesses, contains, or is associated with a historic hut.
-
C.
hasMountainHut
Indicates that one entity possesses, contains, or is associated with a mountain hut located within its area or domain.
-
D.
hasHome
Indicates that an entity possesses or is associated with a place where it lives or is based.
-
E.
hasAssociatedHabitat
Indicates that an entity is linked to a particular habitat in which it typically lives, occurs, or is found.
- 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_69e77e881fc08190ba1c8dc7e2a07f97 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f63639a84c81909d700a539b458b42 |
completed | May 2, 2026, 5:36 p.m. |
| PD | Predicate disambiguation | batch_69f63182f1408190bddc1214fcbd6145 |
completed | May 2, 2026, 5:16 p.m. |
| PDg | Predicate description generation | batch_69f6352df6148190bc10772cd40bd7b3 |
completed | May 2, 2026, 5:32 p.m. |
Created at: April 22, 2026, 8:54 a.m.