Triple
T22871490
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Praia de Gaibu |
E567206
|
entity |
| Predicate | temUsoPrincipal |
P125948
|
FINISHED |
| Object | lazer e turismo |
—
|
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: lazer e turismo | Statement: [Praia de Gaibu, temUsoPrincipal, lazer e turismo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: temUsoPrincipal Context triple: [Praia de Gaibu, temUsoPrincipal, lazer e turismo]
-
A.
isPrimarilyUsedAs
chosen
Indicates that one entity serves mainly or most commonly in the role, function, or purpose specified by the other entity.
-
B.
primaryUseOf
Indicates that one entity serves as the main or principal function, purpose, or application of another entity.
-
C.
usedPrimarilyIn
Indicates that something is mainly or most commonly employed within a particular context, domain, or purpose.
-
D.
primaryUseStart
Indicates the point in time or event at which the primary use or main function of something begins.
-
E.
laterPrimarilyUsedFor
Indicates that something was initially used for one purpose but, at a later time, came to be used mainly for another specified purpose.
- 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.