Triple
T25773666
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Ben |
E649086
|
entity |
| Predicate | winterConditionsMayInclude |
P38722
|
FINISHED |
| Object | snow and ice |
—
|
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: snow and ice | Statement: [The Ben, winterConditionsMayInclude, snow and ice]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: winterConditionsMayInclude Context triple: [The Ben, winterConditionsMayInclude, snow and ice]
-
A.
winterCharacteristic
Indicates a characteristic, feature, or quality that is specifically associated with or typical of winter.
-
B.
winterStatus
chosen
Indicates the condition, phase, or circumstances associated with the winter season for a given entity or context.
-
C.
winterAccessMode
Indicates how access to something is configured, permitted, or restricted specifically during the winter season.
-
D.
winterForageDependsOn
Indicates that the availability or quality of winter forage is contingent upon, or influenced by, another factor or resource.
-
E.
winterFrequency
Indicates how often the related event, condition, or phenomenon occurs during the winter season.
- 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_69e7ab333b508190b6d708d8d9a328ed |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f5fe5b23ac81908ff1b6f06911f45b |
completed | May 2, 2026, 1:38 p.m. |
| PD | Predicate disambiguation | batch_69f4938b960081909b53c074a3e0c7c2 |
completed | May 1, 2026, 11:50 a.m. |
Created at: April 22, 2026, 5:32 a.m.