Triple
T33436278
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DOM Level 2 |
E856245
|
entity |
| Predicate | definesModule |
P196959
|
FINISHED |
| Object | DOM Level 2 Core |
—
|
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: DOM Level 2 Core | Statement: [DOM Level 2, definesModule, DOM Level 2 Core]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: definesModule Context triple: [DOM Level 2, definesModule, DOM Level 2 Core]
-
A.
moduleOf
Indicates that one entity functions as a component or sub-unit that belongs to, or is contained within, another larger entity.
-
B.
definesComponent
Indicates that one entity specifies or establishes the structure, behavior, or characteristics of another entity as its component.
-
C.
definesMIBModule
Indicates that one entity specifies or establishes the structure and contents of a particular MIB (Management Information Base) module for network management.
-
D.
definesService
Indicates that one entity specifies or establishes the service provided or implemented by another entity.
-
E.
introducesModule
Indicates that one entity presents, initiates, or brings another entity (a module) into use, context, or awareness.
- 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_69f349709e7881908c342b4d34f555f4 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fe6fea4a288190bf8615c5d6bf41b4 |
completed | May 8, 2026, 11:21 p.m. |
| PD | Predicate disambiguation | batch_69fe6f774de08190975a2393b9a1fd22 |
completed | May 8, 2026, 11:19 p.m. |
| PDg | Predicate description generation | batch_69fe6fe98e38819085100ce4c6cee5b8 |
completed | May 8, 2026, 11:21 p.m. |
Created at: May 1, 2026, 1:36 a.m.