Triple
T5354010
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aberavon Beach |
E102644
|
entity |
| Predicate | hasPromenadeLength |
P63203
|
FINISHED |
| Object | approximately 3 kilometres |
—
|
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: approximately 3 kilometres | Statement: [Aberavon Beach, hasPromenadeLength, approximately 3 kilometres]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPromenadeLength Context triple: [Aberavon Beach, hasPromenadeLength, approximately 3 kilometres]
-
A.
hasPromenade
Indicates that one entity features or includes a promenade, typically as a designated walkway or leisure area associated with it.
-
B.
hasPedestrianPlazaOn
Indicates that a pedestrian plaza is located on, or directly associated with, a specified surface, structure, or area.
-
C.
roadLength
Indicates the measured distance or extent of a road, typically expressed in units of length.
-
D.
hasPedestrianArea
Indicates that a location or zone includes a designated area intended for pedestrian use only or primarily.
-
E.
trailLengthApprox
Indicates an approximate measurement of the total length of a trail.
- 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_69bd43d8f7248190b64c140734b5c9a8 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd86149774819084049a8785e3f2e0 |
completed | March 20, 2026, 5:38 p.m. |
| PD | Predicate disambiguation | batch_69bd845c6f108190832a8d14b356368a |
completed | March 20, 2026, 5:31 p.m. |
| PDg | Predicate description generation | batch_69bd85e69e808190b29548670fd2900a |
completed | March 20, 2026, 5:37 p.m. |
Created at: March 20, 2026, 2:01 p.m.