Triple
T15835050
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | G3-PLC |
E383963
|
entity |
| Predicate | usesLayerModel |
P37433
|
FINISHED |
| Object | OSI-like layered architecture |
—
|
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: OSI-like layered architecture | Statement: [G3-PLC, usesLayerModel, OSI-like layered architecture]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesLayerModel Context triple: [G3-PLC, usesLayerModel, OSI-like layered architecture]
-
A.
useOfModel
chosen
Indicates that one entity employs, applies, or relies on a particular model for a specific purpose or task.
-
B.
usesModelsType
Indicates that one entity employs or relies on a specific type or category of models in its operation or behavior.
-
C.
operatesOnLayer
Indicates that an entity performs actions or functions specifically targeting a particular layer within a layered structure or system.
-
D.
layerOf
Indicates that one entity forms a distinct layer or stratum of another entity within a structured or composite whole.
-
E.
usedByModel
Indicates that something (such as a resource, method, or component) is utilized or consumed by a particular model.
- 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_69d86da34c888190976e06c4019d415a |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e11e673e08819080c3f55a225607c7 |
completed | April 16, 2026, 5:37 p.m. |
| PD | Predicate disambiguation | batch_69e005418f588190824d91ff7974dada |
completed | April 15, 2026, 9:38 p.m. |
Created at: April 10, 2026, 4:49 a.m.