Triple
T3697475
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Belle Glade culture |
E78492
|
entity |
| Predicate | environmentAdaptation |
P2375
|
FINISHED |
| Object | wetland adaptation |
—
|
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: wetland adaptation | Statement: [Belle Glade culture, environmentAdaptation, wetland adaptation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: environmentAdaptation Context triple: [Belle Glade culture, environmentAdaptation, wetland adaptation]
-
A.
adaptation
Indicates a relationship where one entity changes or is modified to better suit, function within, or correspond to another entity or context.
-
B.
environmentalCondition
Indicates the state or characteristics of the surrounding physical environment that affect or describe a situation, process, or entity.
-
C.
nativeToClimate
Indicates that an entity naturally originates from or is originally adapted to a specified climate or climatic region.
-
D.
adaptationType
chosen
Indicates the specific kind or category of adaptation that relates one entity to another or to a particular context.
-
E.
environmentType
Indicates the kind or category of environment associated with an entity or situation.
- 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_69ad85e3b1888190abc983e06968696d |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc5115ad8819085ffa938de3943f4 |
completed | March 8, 2026, 6:50 p.m. |
| PD | Predicate disambiguation | batch_69adb84dc5808190850aa6975cb09e27 |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:26 p.m.