Triple
T27583570
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DDS |
E699637
|
entity |
| Predicate | hasWireProtocol |
P9964
|
FINISHED |
| Object | RTPS |
—
|
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: RTPS | Statement: [DDS, hasWireProtocol, RTPS]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWireProtocol Context triple: [DDS, hasWireProtocol, RTPS]
-
A.
hasProtocol
chosen
Indicates that an entity uses, follows, or is governed by a specified protocol or set of procedural rules.
-
B.
isWired
Indicates that one entity is physically connected to another via electrical or data wiring.
-
C.
hasWirePlaneType
Indicates that an entity is associated with or characterized by a specific type of wire plane.
-
D.
hasSubProtocol
Indicates that one protocol is a component, phase, or specialized part of another, more general protocol.
-
E.
hasFlagProtocol
Indicates that an entity is associated with, governed by, or operates under a specific flag protocol or set of flag-related rules.
- 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_69ef6a4cb8b881909b3a8d630fd89df2 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f6691f5e188190b12c7b2eb729a45e |
completed | May 2, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69f66598d6008190a7ca8ff80399fd34 |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 27, 2026, 2:03 p.m.