Triple
T34751811
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Voula beach |
E1001801
|
entity |
| Predicate | hasCoastalPromenade |
P12289
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Voula beach, hasCoastalPromenade, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCoastalPromenade Context triple: [Voula beach, hasCoastalPromenade, true]
-
A.
hasPromenade
chosen
Indicates that one entity features or includes a promenade, typically as a designated walkway or leisure area associated with it.
-
B.
hasBenchesAlongPromenade
Indicates that benches are present along the length or sides of a promenade.
-
C.
hasBeachNearby
Indicates that one location is situated close enough to another location to have convenient access to a beach.
-
D.
hasBeach
Indicates that one entity possesses, includes, or is characterized by a beach as part of its features or environment.
-
E.
hasBeachSection
Indicates that an area, location, or property includes or is associated with a specific section designated as 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_69f76db0fb30819096709d43f9a1f45f |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379fd7aac8190873077e63873aa72 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 3:59 p.m.