Triple
T24130240
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paradise Beach |
E597928
|
entity |
| Predicate | hasPrimaryTerrain |
P154951
|
FINISHED |
| Object | sand |
—
|
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: sand | Statement: [Paradise Beach, hasPrimaryTerrain, sand]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrimaryTerrain Context triple: [Paradise Beach, hasPrimaryTerrain, sand]
-
A.
hasTerrainFor
Indicates that a location or area possesses terrain suitable or designated for a particular use, activity, or feature.
-
B.
hasIntermediateTerrain
Indicates that something is situated on or characterized by terrain of medium or moderate difficulty or ruggedness, between easy/flat and difficult/extreme terrain.
-
C.
hasAdvancedTerrain
Indicates that an entity possesses or is associated with terrain featuring complex, challenging, or enhanced physical characteristics beyond standard ground conditions.
-
D.
hasRockyTerrain
Indicates that the subject possesses or is characterized by rough, uneven, or rock-covered ground or surface conditions.
-
E.
hasTerrainCharacter
Indicates that one entity possesses or exhibits a particular terrain-related feature or characteristic in relation to another entity.
- 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_69e288c808b881909fed7d18f04bcbbe |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1df7644808190b4bbbf4db1539f48 |
completed | April 29, 2026, 10:37 a.m. |
| PD | Predicate disambiguation | batch_69f1765650fc8190a6bc1eb512b240bf |
completed | April 29, 2026, 3:09 a.m. |
| PDg | Predicate description generation | batch_69f17c28b684819084eea522126463f8 |
completed | April 29, 2026, 3:34 a.m. |
Created at: April 17, 2026, 11:24 p.m.