Triple
T29690964
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Extended Window Manager Hints |
E751207
|
entity |
| Predicate | definesPropertyPrefix |
P66290
|
FINISHED |
| Object | _NET_ |
—
|
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: _NET_ | Statement: [Extended Window Manager Hints, definesPropertyPrefix, _NET_]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: definesPropertyPrefix Context triple: [Extended Window Manager Hints, definesPropertyPrefix, _NET_]
-
A.
namespacePrefix
chosen
Indicates the abbreviated prefix string associated with a particular namespace URI in a naming or identifier system.
-
B.
namePrefix
Indicates that one entity is a prefix or leading part of another entity’s name.
-
C.
encodingPrefix
Indicates that one encoding scheme or representation serves as the initial or leading segment of another encoding.
-
D.
prototypeProperty
Indicates that one entity serves as a prototype or template from which the other entity derives its structure, behavior, or characteristics.
-
E.
configurableProperty
Indicates that an entity has a setting or attribute whose value can be adjusted or customized, typically to modify its behavior or characteristics.
- 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_69f0d625b09481909b0b69aea1e846c8 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69fd2a215d6c8190a1a428ccaee603f1 |
completed | May 8, 2026, 12:11 a.m. |
| PD | Predicate disambiguation | batch_69fd28ef19688190bb8370f2812a43e7 |
completed | May 8, 2026, 12:06 a.m. |
Created at: April 28, 2026, 7:16 p.m.