Triple
T32490735
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Echo Protocol |
E830376
|
entity |
| Predicate | connectionOrientedSupport |
P166182
|
FINISHED |
| Object | TCP mode |
—
|
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: TCP mode | Statement: [Echo Protocol, connectionOrientedSupport, TCP mode]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: connectionOrientedSupport Context triple: [Echo Protocol, connectionOrientedSupport, TCP mode]
-
A.
isConnectionOriented
chosen
Indicates that the communication or interaction requires establishing and maintaining a dedicated connection between parties for its duration.
-
B.
connectionDirection
Indicates the directional flow or orientation of a connection from one entity to another.
-
C.
isConnectionless
Indicates that the communication or interaction occurs without establishing or maintaining a dedicated, persistent connection between the participating entities.
-
D.
laterSupportedDuplexMode
Indicates that one entity provided support for duplex mode at a later time than another entity.
-
E.
connectionSemantics
Indicates the nature or rules of how entities are linked or related within a given context.
- 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_69f34920aa4081908d8fb0277414b911 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fed48d8e148190a99c0aea29f8a3ee |
completed | May 9, 2026, 6:30 a.m. |
| PD | Predicate disambiguation | batch_69fed3c82a24819095e614e31ac0307f |
completed | May 9, 2026, 6:27 a.m. |
Created at: May 1, 2026, 12:59 a.m.