Triple
T25389671
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Magnetic Island |
E636125
|
entity |
| Predicate | hasMainBeach |
P133316
|
FINISHED |
| Object | Horseshoe Bay 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: Horseshoe Bay Beach | Statement: [Magnetic Island, hasMainBeach, Horseshoe Bay Beach]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMainBeach Context triple: [Magnetic Island, hasMainBeach, Horseshoe Bay Beach]
-
A.
hasBeach
Indicates that one entity possesses, includes, or is characterized by a beach as part of its features or environment.
-
B.
isMajorBeachOf
chosen
Indicates that a beach is one of the primary or most significant beaches associated with a particular area, region, or body of water.
-
C.
hasBeachSection
Indicates that an area, location, or property includes or is associated with a specific section designated as a beach.
-
D.
hasBeachCharacteristic
Indicates that something possesses a specific quality, feature, or attribute associated with a beach.
-
E.
hasBeachNearby
Indicates that one location is situated close enough to another location to have convenient access to a beach.
- 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_69e75db263888190b77fff9e2827b9a2 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f707f7959881908f037f0d6b1d0c36 |
completed | May 3, 2026, 8:31 a.m. |
| PD | Predicate disambiguation | batch_69f700fc274c8190a128593dc7c7abd0 |
completed | May 3, 2026, 8:02 a.m. |
Created at: April 21, 2026, 1:49 p.m.