Triple
T29738576
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SNA |
E752535
|
entity |
| Predicate | networkModelType |
P39807
|
FINISHED |
| Object | connection-oriented |
—
|
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: connection-oriented | Statement: [SNA, networkModelType, connection-oriented]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: networkModelType Context triple: [SNA, networkModelType, connection-oriented]
-
A.
networkModel
chosen
Indicates a relationship where an entity is represented or organized according to a specific network-based structure or framework.
-
B.
networkType
Indicates the category or kind of network associated with or used by an entity (e.g., wired, wireless, virtual, or specific protocol-based networks).
-
C.
networkShowType
Indicates the type or category of a show as classified by or within a particular network.
-
D.
networkInterfaceType
Indicates the specific kind or category of network interface used to connect entities within a network.
-
E.
networkFamily
Indicates a relationship where entities belong to the same network grouping or family, typically sharing common infrastructure, protocols, or organizational affiliation.
- 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_69f0d62b064081908c1ae61cd68fb139 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f697eabb048190bc01a830f14942c6 |
completed | May 3, 2026, 12:33 a.m. |
| PD | Predicate disambiguation | batch_69f69664142c8190bc695501056b0236 |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 28, 2026, 7:46 p.m.