Triple
T28836315
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Daytime Protocol |
E728193
|
entity |
| Predicate | hasStandardPort |
P2552
|
FINISHED |
| Object | 13 |
—
|
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: 13 | Statement: [Daytime Protocol, hasStandardPort, 13]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStandardPort Context triple: [Daytime Protocol, hasStandardPort, 13]
-
A.
hasUserPort
Indicates that an entity is associated with, exposes, or is accessible through a specific user-facing port or interface.
-
B.
isPortFor
Indicates that one entity serves as a port, interface, or connection point for another entity.
-
C.
typicalPort
Indicates that a specified port is commonly or normally used for a given service, protocol, or application.
-
D.
defaultPort
chosen
Indicates that one entity serves as the standard or preconfigured communication port used by another entity unless explicitly overridden.
-
E.
hasPortName
Indicates that one entity is identified by or associated with a specific port name.
- 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_69f0319dc6088190bbfaa206d40ed74a |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69fd6a1c1c4881908090053bc359b181 |
completed | May 8, 2026, 4:44 a.m. |
| PD | Predicate disambiguation | batch_69fd696f24d8819091033afacbdaadc5 |
completed | May 8, 2026, 4:41 a.m. |
Created at: April 28, 2026, 6:39 a.m.