Triple
T27612352
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Time Protocol |
E700358
|
entity |
| Predicate | isConnectionOriented |
P166182
|
FINISHED |
| Object | true (over TCP) |
—
|
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 TCP) | Statement: [Time Protocol, isConnectionOriented, true (over TCP)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isConnectionOriented Context triple: [Time Protocol, isConnectionOriented, true (over TCP)]
-
A.
isDirectConnection
Indicates that there is an immediate, unmediated link or relationship between two entities without any intermediate steps or nodes.
-
B.
connectionDirection
Indicates the directional flow or orientation of a connection from one entity to another.
-
C.
hasConnection
Indicates that there exists a link, association, or relationship between two entities.
-
D.
compatibleConnection
Indicates that two entities can be connected or used together without conflict, supporting proper operation or interaction.
-
E.
hasModeConnection
Indicates a relationship where one entity is linked to another through a specific mode, method, or type of connection.
- 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_69f66003a3f48190a2ba6da5aafbb5cb |
completed | May 2, 2026, 8:35 p.m. |
| PD | Predicate disambiguation | batch_69f65c2198208190a3954086c22cfcbf |
completed | May 2, 2026, 8:18 p.m. |
| PDg | Predicate description generation | batch_69f65f75ac608190a62cd6afce14f68e |
completed | May 2, 2026, 8:32 p.m. |
Created at: April 27, 2026, 2:11 p.m.