Triple
T22871462
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Praia de Gaibu |
E567206
|
entity |
| Predicate | éConhecidaPor |
P111120
|
FINISHED |
| Object | paisagem cê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: paisagem cênica | Statement: [Praia de Gaibu, éConhecidaPor, paisagem cênica]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: éConhecidaPor Context triple: [Praia de Gaibu, éConhecidaPor, paisagem cênica]
-
A.
reconocidaPor
Indicates that an entity is recognized, acknowledged, or honored by another entity.
-
B.
knownIn
Indicates that an entity is recognized, acknowledged, or familiar within a particular context, domain, or group.
-
C.
segmentKnownFor
Indicates that a specific segment or portion of something is recognized or notable for a particular characteristic, feature, or association.
-
D.
referentKnownFor
chosen
Indicates that the referent is widely recognized or notable for a particular activity, role, achievement, or characteristic.
-
E.
oftenRecognizedBy
Indicates that one entity is frequently identified, acknowledged, or noticed by another entity.
- 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.