Triple
T23312810
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Common Alerting Protocol |
E590626
|
entity |
| Predicate | supportsTransportOver |
P151824
|
FINISHED |
| Object | IP networks |
—
|
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: IP networks | Statement: [Common Alerting Protocol, supportsTransportOver, IP networks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsTransportOver Context triple: [Common Alerting Protocol, supportsTransportOver, IP networks]
-
A.
supportsTransportIntegrationWith
Indicates that one entity enables or is compatible with the integration of transport or transportation-related systems, services, or data with another entity.
-
B.
supportsHandoverWith
Indicates that one entity is capable of transferring control, responsibility, or an ongoing process to another entity in a coordinated handover.
-
C.
allowedTransport
Indicates that a particular mode or means of transport is permitted for use between the related entities.
-
D.
usesTransport
Indicates that an entity employs or relies on a particular mode or means of transportation to move from one place to another.
-
E.
supportsPort
Indicates that one entity is capable of handling, providing, or being compatible with a specified port or port 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_69e25d1d32188190948eb76909d1dcc3 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1972ca70481909e2415c65964210a |
completed | April 29, 2026, 5:29 a.m. |
| PD | Predicate disambiguation | batch_69effcf8ca2c8190887d4f4656617d21 |
completed | April 28, 2026, 12:19 a.m. |
| PDg | Predicate description generation | batch_69f01d88b4ec8190a2a17a88e0eda178 |
completed | April 28, 2026, 2:38 a.m. |
Created at: April 17, 2026, 5:06 p.m.