Triple
T21950498
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Charney–Eliassen model |
E542053
|
entity |
| Predicate | basicState |
P135574
|
FINISHED |
| Object | zonal mean flow |
—
|
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: zonal mean flow | Statement: [Charney–Eliassen model, basicState, zonal mean flow]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: basicState Context triple: [Charney–Eliassen model, basicState, zonal mean flow]
-
A.
standardState
Indicates that an entity is in its default, reference, or officially recognized condition or configuration under standard conditions.
-
B.
principalState
Indicates that an entity serves as the primary or main state associated with another entity or context.
-
C.
stateBase
chosen
Indicates that an entity serves as the foundational or primary state upon which another state or condition is defined or derived.
-
D.
builtInState
Indicates that an entity was constructed or established within a particular state or region.
-
E.
secondaryState
Indicates that an entity is in a subordinate or less primary condition, status, or mode relative to its main or primary state.
- 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_69e0c47ef0e48190a50e1bcc43f4b3fd |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f1243bb9c88190a3774b9fa2af9871 |
completed | April 28, 2026, 9:18 p.m. |
| PD | Predicate disambiguation | batch_69e6f601f2188190893bcdde0cf58ad6 |
completed | April 21, 2026, 3:58 a.m. |
Created at: April 16, 2026, 7:58 p.m.