Triple
T7936372
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Domino HTTP task |
E184297
|
entity |
| Predicate | listensOnPort |
P11580
|
FINISHED |
| Object | 80 |
—
|
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: 80 | Statement: [Domino HTTP task, listensOnPort, 80]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: listensOnPort Context triple: [Domino HTTP task, listensOnPort, 80]
-
A.
hasPortOn
Indicates that one entity possesses or is located adjacent to a port situated on another specified geographic or infrastructural feature (such as a coast, river, or lake).
-
B.
registeredPort
Indicates that a specific network port number has been officially assigned and recorded for use by a particular service or protocol.
-
C.
portNumber
Indicates the specific communication port assigned to a network connection, service, or endpoint.
-
D.
openedPort
Indicates that a network port on a host or device is currently open and able to accept incoming connections.
-
E.
usedOnPort
chosen
Indicates that something is applied, connected, or operates specifically on a given port.
- 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_69ca8290c21c8190906a5ca6fe2b03c4 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb3aede3cc81908b0d3b54e68997b9 |
completed | March 31, 2026, 3:09 a.m. |
| PD | Predicate disambiguation | batch_69cae9335f288190ba96781fd6576a2b |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 5:08 p.m.