Triple
T27531226
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sant’Angelo harbor |
E694977
|
entity |
| Predicate | isWaterfrontFocalPointOf |
P114692
|
FINISHED |
| Object | Sant’Angelo |
—
|
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: Sant’Angelo | Statement: [Sant’Angelo harbor, isWaterfrontFocalPointOf, Sant’Angelo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isWaterfrontFocalPointOf Context triple: [Sant’Angelo harbor, isWaterfrontFocalPointOf, Sant’Angelo]
-
A.
isCentralWaterfrontOf
chosen
Indicates that one location serves as the primary waterfront area or main waterside district of another place.
-
B.
isWaterfrontSettlement
Indicates that a settlement is located directly adjacent to a body of water, such as a sea, lake, or river.
-
C.
isWaterfrontThoroughfare
Indicates that a thoroughfare (such as a road, street, or path) is located directly along or adjacent to a body of water.
-
D.
hasWaterfrontType
Indicates that an entity is associated with a specific type or category of waterfront (e.g., oceanfront, lakefront, riverfront).
-
E.
isWaterfrontBuilding
Indicates that a building is located directly adjacent to a body of water, such as a river, lake, or ocean.
- 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_69ef538608b081908b9f659bb09d5e0f |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f62f56b78c81908ad93682bf05f888 |
completed | May 2, 2026, 5:07 p.m. |
| PD | Predicate disambiguation | batch_69f623ac3a9c8190a6ee0c137b09e4b0 |
completed | May 2, 2026, 4:17 p.m. |
Created at: April 27, 2026, 1:26 p.m.