Triple
T27584887
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Meta Object Facility |
E699667
|
entity |
| Predicate | includesSubspecification |
P151825
|
FINISHED |
| Object | Essential MOF |
—
|
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: Essential MOF | Statement: [Meta Object Facility, includesSubspecification, Essential MOF]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesSubspecification Context triple: [Meta Object Facility, includesSubspecification, Essential MOF]
-
A.
includesSubmodule
Indicates that one module contains another module as a subordinate or component part within its structure.
-
B.
extendsSpecificationDefinedIn
chosen
Indicates that one specification builds upon, elaborates, or broadens the scope of another previously defined specification.
-
C.
subsumedBy
Indicates that one entity is more specific and fully contained within another, more general entity in a hierarchical or set-inclusion sense.
-
D.
isSubsegmentOf
Indicates that one segment is entirely contained within and forms a continuous part of another, larger segment.
-
E.
specializesTo
Indicates that one entity is a more specific or specialized version of another, inheriting its characteristics while adding further constraints or detail.
- 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_69ef6a4cb8b881909b3a8d630fd89df2 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69fe163a41a0819098403b470e327d29 |
completed | May 8, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69fe1358db5c819092570814a37ef5bd |
completed | May 8, 2026, 4:46 p.m. |
Created at: April 27, 2026, 2:04 p.m.