Triple
T29952257
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vale do Paraíba e Litoral Norte |
E760799
|
entity |
| Predicate | coastalSubregion |
P156876
|
FINISHED |
| Object | Litoral Norte de São Paulo |
—
|
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: Litoral Norte de São Paulo | Statement: [Vale do Paraíba e Litoral Norte, coastalSubregion, Litoral Norte de São Paulo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coastalSubregion Context triple: [Vale do Paraíba e Litoral Norte, coastalSubregion, Litoral Norte de São Paulo]
-
A.
hasCoastalRegion
Indicates that a place possesses at least one region that borders or is directly adjacent to a sea or ocean.
-
B.
isCoastalRegion
Indicates that a region is located along or directly adjacent to a sea or ocean coastline.
-
C.
areCoastal
Indicates that the entities are located on or adjacent to a coastline or seashore.
-
D.
continentCoast
Indicates that a continent has a coastline along, or is bordered by, a particular body of water or coastal region.
-
E.
isInCoastalRegion
chosen
Indicates that a location or area is situated within a coastal region, typically near or along a sea or ocean shoreline.
- 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_69f2246562b881909d57622f4086d43d |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f67837aa6c8190a74eea05d3a6c4b1 |
completed | May 2, 2026, 10:18 p.m. |
| PD | Predicate disambiguation | batch_69f66ec8298c8190b41fe9d182c05676 |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 29, 2026, 6:26 p.m.