Triple
T28522707
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | StokerCon |
E721828
|
entity |
| Predicate | hasNetworkingFunction |
P194604
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [StokerCon, hasNetworkingFunction, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNetworkingFunction Context triple: [StokerCon, hasNetworkingFunction, yes]
-
A.
hasNet
Indicates that one entity possesses, is equipped with, or includes a net.
-
B.
hasPrimaryNetwork
Indicates that an entity is associated with or connected to its main or most important network among potentially multiple networks.
-
C.
supportsNetworkingModel
Indicates that one entity provides compatibility with, or implementation of, a specified networking model for another entity.
-
D.
hasNetworkStructure
Indicates that one entity possesses, exhibits, or is organized according to a particular network-based structure defined by another entity or specification.
-
E.
hasNetworkElement
Indicates that one entity includes, contains, or is associated with a specific network element as part of its network structure or configuration.
- 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_69f01a5cbcc4819083fb4e723378713e |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69fd7e364a648190a1e9e1d9fc76e99e |
completed | May 8, 2026, 6:09 a.m. |
| PD | Predicate disambiguation | batch_69fd7bb547608190a3b04dddbca6b8bc |
completed | May 8, 2026, 5:59 a.m. |
| PDg | Predicate description generation | batch_69fd7e35967081909f8bc8389d976ffd |
completed | May 8, 2026, 6:09 a.m. |
Created at: April 28, 2026, 3:22 a.m.