Triple
T29564944
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gomerans |
E753137
|
entity |
| Predicate | communicationAdaptedTo |
P30779
|
FINISHED |
| Object | rugged topography of La Gomera |
—
|
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: rugged topography of La Gomera | Statement: [Gomerans, communicationAdaptedTo, rugged topography of La Gomera]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: communicationAdaptedTo Context triple: [Gomerans, communicationAdaptedTo, rugged topography of La Gomera]
-
A.
communicationEffect
Indicates that one entity’s act of communication causes a change or effect in another entity’s state, behavior, or information.
-
B.
communicationModel
chosen
Indicates the type or framework of communication used or assumed in the relationship between entities.
-
C.
communicationPrinciple
Indicates a guiding rule or norm that shapes how communication should be conducted between entities.
-
D.
communicationService
Indicates a relationship where one entity provides or facilitates a means for another entity to exchange information or messages.
-
E.
communicationUnderstoodBy
Indicates that a communicated message or information is successfully comprehended by the receiving 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_69f0ef7fcb4881908a933110adb9bda1 |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_69f69dfdda708190be290c7bec205445 |
completed | May 3, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69f69d1a37e081908d1d86b90ff502bd |
completed | May 3, 2026, 12:55 a.m. |
Created at: April 28, 2026, 5:51 p.m.