Triple
T22871455
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Praia de Gaibu |
E567206
|
entity |
| Predicate | temTipoDeAmbiente |
P853
|
FINISHED |
| Object | praia oceânica |
—
|
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: praia oceânica | Statement: [Praia de Gaibu, temTipoDeAmbiente, praia oceânica]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: temTipoDeAmbiente Context triple: [Praia de Gaibu, temTipoDeAmbiente, praia oceânica]
-
A.
environmentType
chosen
Indicates the kind or category of environment associated with an entity or situation.
-
B.
environmentAnalogOf
Indicates that one environment serves as an analogue or counterpart to another, typically mirroring its conditions, structure, or behavior for comparison or simulation purposes.
-
C.
ambientSpace
Indicates the surrounding or containing space within which an object, structure, or geometric entity is situated or defined.
-
D.
spaceType
Indicates the category or kind of physical or conceptual space associated with an entity.
-
E.
environmentalMode
Indicates that an entity operates in or is configured to a specific environmental setting or condition (such as eco, normal, or high-performance mode).
- 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_69e24589d8348190b96422d13a678bc1 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17f05c688819097ba3d24ea8e52f5 |
completed | April 29, 2026, 3:46 a.m. |
| PD | Predicate disambiguation | batch_69eed2d8c0608190afef4c4e530c0e2c |
completed | April 27, 2026, 3:07 a.m. |
Created at: April 17, 2026, 3:38 p.m.