Triple
T22815127
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DCCP |
E565076
|
entity |
| Predicate | connectionSemantics |
P149842
|
FINISHED |
| Object | connection-oriented control with unreliable data |
—
|
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 control with unreliable data | Statement: [DCCP, connectionSemantics, connection-oriented control with unreliable data]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: connectionSemantics Context triple: [DCCP, connectionSemantics, connection-oriented control with unreliable data]
-
A.
connectionDirection
Indicates the directional flow or orientation of a connection from one entity to another.
-
B.
connectsWithin
Indicates that one entity establishes a connection or link between elements that lie inside the bounds or scope of another entity.
-
C.
connectionTo
Indicates a relationship in which one entity is linked, associated, or otherwise related to another entity.
-
D.
connectionStandard
Indicates the technical standard or protocol that defines how a connection between entities is established and operates.
-
E.
connectivity
Indicates...the existence, degree, or quality of a link or communication pathway between entities, allowing interaction or information flow between them.
- 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_69e2458426188190b58b8ab4844fe420 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17dcb872881909a031d8560635fce |
completed | April 29, 2026, 3:40 a.m. |
| PD | Predicate disambiguation | batch_69eed2cb30f481909566369f515f6eff |
completed | April 27, 2026, 3:06 a.m. |
| PDg | Predicate description generation | batch_69eeeb577e2081909f4a4e9c296535c0 |
completed | April 27, 2026, 4:51 a.m. |
Created at: April 17, 2026, 3:33 p.m.