Triple
T13619799
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | palafitos of Pedro Montt |
E325418
|
entity |
| Predicate | constructionAdaptation |
P110450
|
FINISHED |
| Object | adapted to tidal changes |
—
|
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: adapted to tidal changes | Statement: [palafitos of Pedro Montt, constructionAdaptation, adapted to tidal changes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: constructionAdaptation Context triple: [palafitos of Pedro Montt, constructionAdaptation, adapted to tidal changes]
-
A.
constructionType
Indicates the specific method or style by which something is built or constructed.
-
B.
constructionBase
Indicates that one entity serves as the foundational structure or base upon which another entity is constructed or built.
-
C.
constructionDirection
Indicates the orientation or path along which a structure is built or assembled.
-
D.
constructionExpanded
Indicates that a construction project or structure has been enlarged or extended beyond its original size or scope.
-
E.
constructionSite
Indicates that an entity is a location or area where construction work is actively taking place or is planned to occur.
- F. None of above. chosen
Provenance (4 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_69d8076aae28819092cf636190ee5529 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbbb9ee3f081909056dc1a92c40b7a |
completed | April 12, 2026, 3:34 p.m. |
| PD | Predicate disambiguation | batch_69dbae1b3ee481909bd43ded6227a3e5 |
completed | April 12, 2026, 2:37 p.m. |
| PDg | Predicate description generation | batch_69dbbb8c77dc8190b7bd803b5e168d23 |
completed | April 12, 2026, 3:34 p.m. |
Created at: April 9, 2026, 9:50 p.m.