Triple
T35602700
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CFM |
E1028798
|
entity |
| Predicate | hasLayeringConcept |
P92765
|
FINISHED |
| Object | maintenance levels |
—
|
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: maintenance levels | Statement: [CFM, hasLayeringConcept, maintenance levels]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLayeringConcept Context triple: [CFM, hasLayeringConcept, maintenance levels]
-
A.
definesLayering
Indicates that one entity specifies or establishes the layering structure or order of layers for another entity.
-
B.
isTypicallyLayered
Indicates that something is usually composed of multiple distinct layers arranged one on top of another.
-
C.
isLayeredOver
Indicates that one entity is positioned or arranged directly on top of another, partially or fully covering it in a layered manner.
-
D.
supportsLayerHierarchy
chosen
Indicates that one element can contain and organize other elements within a structured, ordered layer system.
-
E.
layerOf
Indicates that one entity forms a distinct layer or stratum of another entity within a structured or composite whole.
- 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_69f76e0598dc8190a6a093e904b9aa70 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69ff8cecbf048190860b9f72b8753f5c |
completed | May 9, 2026, 7:37 p.m. |
| PD | Predicate disambiguation | batch_69ff8c4c39dc8190b5bf35adc1bae7c6 |
completed | May 9, 2026, 7:34 p.m. |
Created at: May 3, 2026, 4:05 p.m.