Triple
T28828557
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Odyssey (cancelled NT-based project) |
E727979
|
entity |
| Predicate | intendedKernelBase |
P180786
|
FINISHED |
| Object | Windows NT |
—
|
NE NERFINISHED |
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: Windows NT | Statement: [Odyssey (cancelled NT-based project), intendedKernelBase, Windows NT]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: intendedKernelBase Context triple: [Odyssey (cancelled NT-based project), intendedKernelBase, Windows NT]
-
A.
typicalKernelABI
Indicates that one entity uses or conforms to the other entity as its standard or default kernel-level application binary interface (ABI).
-
B.
primaryKernelType
Indicates that one entity is the main or default kernel type associated with another entity.
-
C.
kernelConsistsOf
Indicates that a kernel is composed of or made up from the specified constituent elements or components.
-
D.
intendedBaseService
Indicates that one service is designed or designated to function as the foundational or primary service upon which another service depends or is built.
-
E.
kernelFamily
Indicates that one kernel is a member of, or derived from, a particular family or class of related kernels.
- 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_69f0319dc6088190bbfaa206d40ed74a |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f7516d5b4081908588a6feb541f355 |
completed | May 3, 2026, 1:45 p.m. |
| PD | Predicate disambiguation | batch_69f74d40ebb081909daf60623e38f41d |
completed | May 3, 2026, 1:27 p.m. |
| PDg | Predicate description generation | batch_69f7516c538481908c6e55cf76add098 |
completed | May 3, 2026, 1:45 p.m. |
Created at: April 28, 2026, 6:36 a.m.