Triple
T14315090
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ethernet switch |
E354934
|
entity |
| Predicate | storesMACTableIn |
P113931
|
FINISHED |
| Object | CAM table |
—
|
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: CAM table | Statement: [Ethernet switch, storesMACTableIn, CAM table]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: storesMACTableIn Context triple: [Ethernet switch, storesMACTableIn, CAM table]
-
A.
storesInterfaceIn
Indicates that one entity keeps or maintains an interface definition within another entity (such as a container, module, or storage location).
-
B.
storesIndexesIn
Indicates that one entity maintains and holds index data within another storage entity or system.
-
C.
storesMetadataIn
Indicates that one entity holds or maintains descriptive or configuration metadata about another entity within a specified storage location or system.
-
D.
storesKeys
Indicates that one entity holds or retains the keys belonging to or used by another entity.
-
E.
storesConfigurationFor
Indicates that one entity holds or maintains configuration settings that are used by or apply to another entity.
- 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_69d8278ed42c8190b9f882dcce611347 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de85b49e5481909b9ffab2d922e284 |
completed | April 14, 2026, 6:21 p.m. |
| PD | Predicate disambiguation | batch_69de2a9515f4819081aabf251bca5878 |
completed | April 14, 2026, 11:52 a.m. |
| PDg | Predicate description generation | batch_69de2e9ded24819099200349cf80e068 |
completed | April 14, 2026, 12:10 p.m. |
Created at: April 10, 2026, 1:12 a.m.