Triple
T6104530
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | America/Havana |
E136082
|
entity |
| Predicate | dstRuleVariability |
P13845
|
FINISHED |
| Object | high |
—
|
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: high | Statement: [America/Havana, dstRuleVariability, high]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dstRuleVariability Context triple: [America/Havana, dstRuleVariability, high]
-
A.
hasDirectionVariability
Indicates that the direction associated with an entity or process is not fixed but varies over time, space, or conditions.
-
B.
dstRulePattern
Indicates a rule-based pattern that specifies or constrains the characteristics of a destination in a relationship or process.
-
C.
hasVariability
chosen
Indicates that an entity exhibits variation or fluctuation in its state, value, or characteristics over time or across instances.
-
D.
displayRule
Indicates the rule or condition that determines how something should be visually presented or displayed.
-
E.
flowVariation
Indicates how the rate or pattern of flow (such as water, traffic, or data) changes over time or across different conditions.
- 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_69c0087dee9881909e3655be88208c01 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c05b3f8e5481909e85a60aaf319f66 |
completed | March 22, 2026, 9:12 p.m. |
| PD | Predicate disambiguation | batch_69c049f80e2081909b7d84a104cda68d |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:13 p.m.