Triple
T24269466
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Windows Western European |
E605236
|
entity |
| Predicate | ianaStatus |
P155391
|
FINISHED |
| Object | registered |
—
|
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: registered | Statement: [Windows Western European, ianaStatus, registered]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ianaStatus Context triple: [Windows Western European, ianaStatus, registered]
-
A.
ICSStatus
Indicates the current state or condition of an entity within an Incident Command System (ICS) context.
-
B.
ICCStatus
Indicates the current standing or classification of an entity with respect to the International Criminal Court (ICC), such as whether it is under investigation, indicted, convicted, or not subject to ICC proceedings.
-
C.
actualStatus
Indicates the current, real-world state or condition of an entity, as opposed to a planned, expected, or nominal status.
-
D.
statusInSI
Indicates that an entity’s status or condition is specified according to the International System of Units (SI) or an SI-based standard.
-
E.
classStatus
Indicates the current academic or enrollment standing of an entity within a class or course context.
- 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_69e2954707dc8190915551eb114cfff6 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f28d58666881909f28f4d4f0f7d590 |
completed | April 29, 2026, 10:59 p.m. |
| PD | Predicate disambiguation | batch_69f1c450aa508190bc9d372a5f6ee47a |
completed | April 29, 2026, 8:41 a.m. |
| PDg | Predicate description generation | batch_69f1c6d4e99081909f61899eccafb73e |
completed | April 29, 2026, 8:52 a.m. |
Created at: April 18, 2026, 12:07 a.m.