Triple
T25343731
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chance Bay |
E635484
|
entity |
| Predicate | connectedByTrackTo |
P118645
|
FINISHED |
| Object | Whitehaven Beach |
—
|
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: Whitehaven Beach | Statement: [Chance Bay, connectedByTrackTo, Whitehaven Beach]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: connectedByTrackTo Context triple: [Chance Bay, connectedByTrackTo, Whitehaven Beach]
-
A.
associatedWithTrack
chosen
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.
-
B.
connectedByPeopleMoverTo
Indicates that two locations are linked by a people mover system that transports people between them.
-
C.
connectedByStraitTo
Indicates that one entity is geographically linked to another by a narrow body of water known as a strait.
-
D.
partlyConnectedBy
Indicates that two entities are linked or joined by something in an incomplete, partial, or not fully continuous way.
-
E.
connectsTo
Indicates a relationship where one entity is linked or joined to another, allowing interaction, communication, or transfer between them.
- 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_69e75a99bd6481909476115b35b9a8e4 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f67c9fe7b48190b79b4041357edb49 |
completed | May 2, 2026, 10:37 p.m. |
| PD | Predicate disambiguation | batch_69f678cc272081909e5c70f1bc7407f0 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 21, 2026, 1:32 p.m.