Triple
T27612353
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Time Protocol |
E700358
|
entity |
| Predicate | isConnectionless |
P166653
|
FINISHED |
| Object | true (over UDP) |
—
|
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: true (over UDP) | Statement: [Time Protocol, isConnectionless, true (over UDP)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isConnectionless Context triple: [Time Protocol, isConnectionless, true (over UDP)]
-
A.
isConnectionOriented
Indicates that the communication or interaction requires establishing and maintaining a dedicated connection between parties for its duration.
-
B.
isDirectConnection
Indicates that there is an immediate, unmediated link or relationship between two entities without any intermediate steps or nodes.
-
C.
hasNoConnectionType
Indicates that there is explicitly no defined type or category of connection between the related entities.
-
D.
isProtocolAgnostic
Indicates that the relationship or mechanism functions independently of any specific communication protocol, working uniformly across different protocols.
-
E.
isLossless
Indicates that a transformation, compression, or process preserves all original information without any loss of data.
- 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_69ef6a4f1d9c8190b0705acda054368d |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f662a29b3881909957a7e3b986653c |
completed | May 2, 2026, 8:46 p.m. |
| PD | Predicate disambiguation | batch_69f660eea4648190b0d5e24293607813 |
completed | May 2, 2026, 8:39 p.m. |
| PDg | Predicate description generation | batch_69f661b47d088190934f63884a203261 |
completed | May 2, 2026, 8:42 p.m. |
Created at: April 27, 2026, 2:11 p.m.