Triple
T13876856
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cabeço Gordo |
E333603
|
entity |
| Predicate | hasViewDescription |
P11875
|
FINISHED |
| Object | panoramic views of the surrounding archipelago |
—
|
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: panoramic views of the surrounding archipelago | Statement: [Cabeço Gordo, hasViewDescription, panoramic views of the surrounding archipelago]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasViewDescription Context triple: [Cabeço Gordo, hasViewDescription, panoramic views of the surrounding archipelago]
-
A.
hasView
Indicates that one entity provides a visual perspective or outlook onto another entity or scene.
-
B.
hasDescription
chosen
Indicates that an entity is associated with a textual description that explains or characterizes it.
-
C.
hasCatalogView
Indicates that an entity is associated with a particular way or mode of viewing or presenting a catalog.
-
D.
hasLevelDescription
Indicates that an entity is associated with a textual description specifying its level, degree, or stage.
-
E.
isViewableIn
Indicates that one entity can be visually accessed, observed, or displayed within the context, medium, or viewpoint defined 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_69d81c5ced9c8190b0e9bcc6effe5959 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de23a101488190bd790b28033d38b9 |
completed | April 14, 2026, 11:23 a.m. |
| PD | Predicate disambiguation | batch_69de05972f3881909977b4c843984f88 |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 9, 2026, 10:15 p.m.