Triple
T28584013
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Luna theme |
E723443
|
entity |
| Predicate | statusInLaterWindows |
P13710
|
FINISHED |
| Object | not default in Windows Vista and later |
—
|
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: not default in Windows Vista and later | Statement: [Luna theme, statusInLaterWindows, not default in Windows Vista and later]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusInLaterWindows Context triple: [Luna theme, statusInLaterWindows, not default in Windows Vista and later]
-
A.
laterStatus
chosen
Indicates that one entity represents a subsequent or resulting status or condition of another entity in time.
-
B.
statusInSuccession
Indicates the position or rank an individual holds within an established line of succession to a title, role, or office.
-
C.
statusPeriod
Indicates the time interval during which a particular status or condition is in effect.
-
D.
statusInSystem7
Indicates that an entity holds a particular status or state within the context of system 7.
-
E.
statusAtTime
Indicates that an entity has a particular status or condition at a specified point in time.
- 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_69f01d7f92e481909847f5f3f3174a89 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69fcef654d588190b29ecc76678d1aa0 |
completed | May 7, 2026, 8 p.m. |
| PD | Predicate disambiguation | batch_69fcecdb97f48190b382b7d13be92dc0 |
completed | May 7, 2026, 7:49 p.m. |
Created at: April 28, 2026, 4:16 a.m.