Triple
T425335
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fibre Channel |
E8194
|
entity |
| Predicate | layerModel |
P6553
|
FINISHED |
| Object | Fibre Channel protocol stack |
—
|
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: Fibre Channel protocol stack | Statement: [Fibre Channel, layerModel, Fibre Channel protocol stack]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: layerModel Context triple: [Fibre Channel, layerModel, Fibre Channel protocol stack]
-
A.
model
Indicates that one entity serves as a representation, example, or simulation of another entity or concept.
-
B.
dataModel
Indicates a relationship where an entity defines, uses, or is structured according to a specific data model or schema.
-
C.
OSIModelLayer
chosen
Indicates the specific layer within the OSI (Open Systems Interconnection) model at which a networking function, protocol, or interaction operates.
-
D.
operationalLayer
Indicates that one entity functions as an operational layer or level through which another entity’s activities, processes, or services are executed or managed.
-
E.
firstModel
Indicates that an entity is the initial or earliest model/version in a sequence or series of models.
- 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_69a2e7f1d1bc81909cf2dc9754a3c334 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2eed56ab481909eec289075496260 |
completed | Feb. 28, 2026, 1:34 p.m. |
| PD | Predicate disambiguation | batch_69a2edd6736c81909a6ca549f77b4345 |
completed | Feb. 28, 2026, 1:29 p.m. |
Created at: Feb. 28, 2026, 1:11 p.m.