Triple
T18513750
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eastern Deciduous Forest |
E452406
|
entity |
| Predicate | typicalDisturbanceRegime |
P131962
|
FINISHED |
| Object | windthrow |
—
|
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: windthrow | Statement: [Eastern Deciduous Forest, typicalDisturbanceRegime, windthrow]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalDisturbanceRegime Context triple: [Eastern Deciduous Forest, typicalDisturbanceRegime, windthrow]
-
A.
disturbanceLevel
Indicates the degree or intensity of disruption, interference, or deviation from a normal or stable state in a given context.
-
B.
typicalDynamics
Indicates the usual or characteristic way in which a system, process, or interaction evolves or behaves over time.
-
C.
typicalStormType
Indicates the kind of storm that is most commonly or characteristically associated with a given context or location.
-
D.
occursInRegime
Indicates that an event, process, or phenomenon takes place within a specific regime, context, or operating condition.
-
E.
hasTypicalIceRegime
Indicates that there is a characteristic or commonly occurring pattern of ice conditions associated with the referenced entity.
- 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_69d8d386df84819092355ebb260d848e |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e53348274c8190a82861b0104538e3 |
completed | April 19, 2026, 7:55 p.m. |
| PD | Predicate disambiguation | batch_69e469dbf5208190b6fc49e02a087f54 |
completed | April 19, 2026, 5:36 a.m. |
| PDg | Predicate description generation | batch_69e46d2b93bc8190a6070018d7046547 |
completed | April 19, 2026, 5:50 a.m. |
Created at: April 10, 2026, 11:36 a.m.