Triple
T32303687
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Praia do Forte (Cabo Frio) |
E825300
|
entity |
| Predicate | isBeachOf |
P1922
|
FINISHED |
| Object | Cabo Frio coastline |
—
|
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: Cabo Frio coastline | Statement: [Praia do Forte (Cabo Frio), isBeachOf, Cabo Frio coastline]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isBeachOf Context triple: [Praia do Forte (Cabo Frio), isBeachOf, Cabo Frio coastline]
-
A.
isTypeOfBeach
Indicates that one entity is classified as a specific type or category of beach in relation to another entity.
-
B.
isBeachTown
Indicates that a place is a town characterized by its location on or near a beach and its association with beach-related activities or environment.
-
C.
hasBeach
chosen
Indicates that one entity possesses, includes, or is characterized by a beach as part of its features or environment.
-
D.
isMajorBeachOf
Indicates that a beach is one of the primary or most significant beaches associated with a particular area, region, or body of water.
-
E.
isOceanBeach
Indicates that a location is a beach situated on or directly adjacent to an 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_69f349115304819084ee91d345b6c8aa |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6bd7ace288190bb6a6b2b300bbd88 |
completed | May 3, 2026, 3:14 a.m. |
| PD | Predicate disambiguation | batch_69f6b632cf788190a3d0c08cd026b84b |
completed | May 3, 2026, 2:42 a.m. |
Created at: May 1, 2026, 12:45 a.m.