Triple
T8716829
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Asian monsoon system |
E206915
|
entity |
| Predicate | summerPhase |
P84066
|
FINISHED |
| Object | moist onshore 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: moist onshore flow | Statement: [Asian monsoon system, summerPhase, moist onshore flow]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: summerPhase Context triple: [Asian monsoon system, summerPhase, moist onshore flow]
-
A.
summerBase
Indicates a base or location where an entity is situated or operates specifically during the summer season.
-
B.
summerWinterCycle
Indicates a recurring transition between summer and winter seasons, capturing the cyclical change in conditions or states across these two periods.
-
C.
summerHomeOf
Indicates that a location serves as a seasonal or vacation residence for a person or group, specifically used during the summer.
-
D.
summerTimeZone
Indicates that a specified region or entity uses a particular time zone during the summer or daylight-saving period.
-
E.
summerRole
Indicates a role, position, or function that an entity holds specifically during the summer period.
- 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_69ca83572d4881909bef3be2b578d539 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5cd9c2a08190a65ab0ce573153d2 |
completed | March 31, 2026, 11:46 p.m. |
| PD | Predicate disambiguation | batch_69cc456e806c819087e7d66ee737f242 |
completed | March 31, 2026, 10:06 p.m. |
| PDg | Predicate description generation | batch_69cc46c40c54819093d174a4203f9515 |
completed | March 31, 2026, 10:12 p.m. |
Created at: March 30, 2026, 6:36 p.m.