Triple
T24412368
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Praia do Tamariz |
E615486
|
entity |
| Predicate | hasPromenadeConnection |
P155825
|
FINISHED |
| Object | Cascais |
—
|
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: Cascais | Statement: [Praia do Tamariz, hasPromenadeConnection, Cascais]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPromenadeConnection Context triple: [Praia do Tamariz, hasPromenadeConnection, Cascais]
-
A.
hasPromenade
Indicates that one entity features or includes a promenade, typically as a designated walkway or leisure area associated with it.
-
B.
hasPromenadeUse
Indicates that something is used or designated for promenade activities, such as walking or leisurely strolling.
-
C.
hasPromenadeLength
Indicates the length or extent of a promenade associated with an entity.
-
D.
hasPromenadeName
Indicates that a promenade is associated with or identified by a specific name.
-
E.
hasPromenadeStyle
Indicates that something features or is characterized by a particular style or manner associated with promenades or promenade-like walking areas.
- 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_69e2d7e9bfac8190a748952a90957106 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f2958241e48190ae33297c5c5c0e59 |
completed | April 29, 2026, 11:34 p.m. |
| PD | Predicate disambiguation | batch_69f287cc4fd4819081e93cc638d9512d |
completed | April 29, 2026, 10:35 p.m. |
| PDg | Predicate description generation | batch_69f2915233c48190a181c8c1924e892c |
completed | April 29, 2026, 11:16 p.m. |
Created at: April 18, 2026, 2:10 a.m.