Triple
T25283644
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Meiyu front |
E633879
|
entity |
| Predicate | formsBetween |
P51111
|
FINISHED |
| Object | cooler continental air mass |
—
|
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: cooler continental air mass | Statement: [Meiyu front, formsBetween, cooler continental air mass]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formsBetween Context triple: [Meiyu front, formsBetween, cooler continental air mass]
-
A.
formsInterchangeBetween
chosen
Indicates that one entity creates or establishes an interchange (e.g., a junction, connection, or transfer point) between two or more other entities.
-
B.
formsWith
Indicates that one entity combines or associates with another to create or constitute a joint structure, group, or configuration.
-
C.
formsInteractingPairWith
Indicates that one entity forms a mutually interacting pair or duo with another entity, such that their behaviors or effects are directly linked.
-
D.
formsIn
Indicates that one entity takes shape, develops, or comes into existence within or inside another entity.
-
E.
formsFrom
Indicates that one entity is created, derived, or takes shape as a result of another 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_69e75a9402fc81909362ca85277c06d9 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f60c3b09488190ade1b69ff7f0df0e |
completed | May 2, 2026, 2:37 p.m. |
| PD | Predicate disambiguation | batch_69f60b8461ac81908c5bd3d73eed59f4 |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 21, 2026, 1:19 p.m.