Triple
T28612193
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Klondike |
E724191
|
entity |
| Predicate | isCommonlyIncludedIn |
P46711
|
FINISHED |
| Object | computer operating systems |
—
|
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: computer operating systems | Statement: [Klondike, isCommonlyIncludedIn, computer operating systems]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isCommonlyIncludedIn Context triple: [Klondike, isCommonlyIncludedIn, computer operating systems]
-
A.
isFrequentlyIncludedIn
chosen
Indicates that something is regularly or commonly contained or made part of something else.
-
B.
sometimesIncluded
Indicates that one entity is occasionally, but not always, contained within, part of, or present in association with another entity.
-
C.
isTypicallyConsumedFrom
Indicates that one entity is most commonly eaten or drunk using, contained in, or taken from the other entity.
-
D.
includedByDefaultIn
Indicates that one entity is automatically present or enabled within another entity or context without requiring explicit selection or configuration.
-
E.
includes
Indicates that one entity contains, encompasses, or has another entity as a part, member, or subset.
- 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_69f01d816d7c8190a1fe27e3434041dc |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f68805b4848190b75da14996d52a38 |
completed | May 2, 2026, 11:25 p.m. |
| PD | Predicate disambiguation | batch_69f68609c0b08190a8e1238a4d97c270 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 28, 2026, 4:30 a.m.