Triple
T10779312
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yungas |
E254274
|
entity |
| Predicate | hasFogFrequency |
P29070
|
FINISHED |
| Object | frequent cloud and mist cover |
—
|
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: frequent cloud and mist cover | Statement: [Yungas, hasFogFrequency, frequent cloud and mist cover]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFogFrequency Context triple: [Yungas, hasFogFrequency, frequent cloud and mist cover]
-
A.
hasFogSignal
Indicates that an entity is equipped with or associated with a fog signal used for navigation or warning in low-visibility conditions.
-
B.
hasFrequencyCategory
Indicates that something is associated with a particular classification of how often it occurs or is used.
-
C.
hasFieldOfView
Indicates that one entity possesses a visual coverage area within which it can perceive or detect other entities or regions.
-
D.
hasFBO
Indicates that one entity has a specified Foreign/Final Beneficial Owner (FBO) associated with it.
-
E.
hasEventFrequency
chosen
Indicates how often a particular event occurs within a given time period.
- 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_69d6aa609f008190a294200aefcb7bd5 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d732c25478819093dedec0c8556777 |
completed | April 9, 2026, 5:01 a.m. |
| PD | Predicate disambiguation | batch_69d6f31455648190b5c24690487b1b54 |
completed | April 9, 2026, 12:30 a.m. |
Created at: April 8, 2026, 9:16 p.m.