Triple
T29738667
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SNA Services |
E752537
|
entity |
| Predicate | supportsNetworkingArchitecture |
P31923
|
FINISHED |
| Object | Systems Network Architecture |
E1882382
|
NE 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: Systems Network Architecture | Statement: [SNA Services, supportsNetworkingArchitecture, Systems Network Architecture]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsNetworkingArchitecture Context triple: [SNA Services, supportsNetworkingArchitecture, Systems Network Architecture]
-
A.
supportsNetworkingModel
chosen
Indicates that one entity provides compatibility with, or implementation of, a specified networking model for another entity.
-
B.
supportsNetworkingLibraries
Indicates that an entity provides compatibility with or functionality for using networking libraries.
-
C.
supportedNetwork
Indicates that one entity (such as a device, service, or application) is compatible with, operates on, or is designed to work over a specified network or type of network.
-
D.
supportedArchitect
Indicates that one entity provides architectural backing, endorsement, or assistance to another entity or architectural concept.
-
E.
supportedArchitectureSite
Indicates that a site or location is designed to support, host, or be compatible with a specified architecture.
- F. None of above.
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_69f0d62b064081908c1ae61cd68fb139 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a26c8e6fa5c81908c63cc4350978226 |
completed | June 8, 2026, 1:51 p.m. |
| PD | Predicate disambiguation | batch_6a0379e0f3d88190a4ee7b0673f1ef90 |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 28, 2026, 7:46 p.m.