Triple
T18020193
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Smugglers Cove |
E431094
|
entity |
| Predicate | hasBeachSurface |
P129445
|
FINISHED |
| Object | mix of sand and pebbles |
—
|
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: mix of sand and pebbles | Statement: [Smugglers Cove, hasBeachSurface, mix of sand and pebbles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBeachSurface Context triple: [Smugglers Cove, hasBeachSurface, mix of sand and pebbles]
-
A.
hasBeach
Indicates that one entity possesses, includes, or is characterized by a beach as part of its features or environment.
-
B.
hasBeachSection
Indicates that an area, location, or property includes or is associated with a specific section designated as a beach.
-
C.
hasBeachSlope
Indicates that a location or coastal area possesses a particular gradient or steepness of its beach surface.
-
D.
hasBeachNearby
Indicates that one location is situated close enough to another location to have convenient access to a beach.
-
E.
hasBeachUse
Indicates that an entity is used for, designated for, or associated with beach-related activities or purposes.
- 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_69d8b904530081908bf341d842464856 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4b9c1c5f88190a059ce4f86f7ed36 |
completed | April 19, 2026, 11:17 a.m. |
| PD | Predicate disambiguation | batch_69e3f904b8048190add43883cd7cb191 |
completed | April 18, 2026, 9:35 p.m. |
| PDg | Predicate description generation | batch_69e42d8eefa88190a700c7c1b4213e46 |
completed | April 19, 2026, 1:19 a.m. |
Created at: April 10, 2026, 10:24 a.m.