Triple
T29126940
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Praia da Bordeira |
E738256
|
entity |
| Predicate | hasNaturalCharacteristic |
P106758
|
FINISHED |
| Object | strong surf |
—
|
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: strong surf | Statement: [Praia da Bordeira, hasNaturalCharacteristic, strong surf]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNaturalCharacteristic Context triple: [Praia da Bordeira, hasNaturalCharacteristic, strong surf]
-
A.
hasNaturalCondition
chosen
Indicates that an entity possesses or is subject to a particular natural state, feature, or condition inherent to its environment or biology.
-
B.
hasHumanCharacteristic
Indicates that an entity possesses a trait, quality, or behavior typically associated with humans.
-
C.
hasNature
Indicates that something possesses, exhibits, or is characterized by a particular inherent quality, essence, or fundamental type.
-
D.
hasNaturalForm
Indicates that an entity possesses an inherent, unaltered, or naturally occurring form or state.
-
E.
isNaturalIn
Indicates that something occurs, exists, or develops in a place or context as a native or inherent part of it, without artificial introduction.
- 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_69f07cb29cdc8190afa55444553de60c |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69fd553d7cb881908d243e7a9f30ac85 |
completed | May 8, 2026, 3:15 a.m. |
| PD | Predicate disambiguation | batch_69fd514dcb1c81908333c70d7edd79c9 |
completed | May 8, 2026, 2:58 a.m. |
Created at: April 28, 2026, 11:29 a.m.