Triple
T32490778
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Discard Protocol |
E830377
|
entity |
| Predicate | hasServiceCode |
P162526
|
FINISHED |
| Object | discard(9/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: discard(9/tcp) | Statement: [Discard Protocol, hasServiceCode, discard(9/tcp)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasServiceCode Context triple: [Discard Protocol, hasServiceCode, discard(9/tcp)]
-
A.
hasServiceTo
Indicates that one entity provides, offers, or operates a service for or directed toward another entity.
-
B.
hasServiceType
Indicates that an entity is associated with or categorized by a particular type of service.
-
C.
hasIneCode
Indicates that an entity is associated with a specific INE (national statistics or education) code that identifies it in an official registry.
-
D.
hasFeatureCode
Indicates that an entity is associated with a specific feature identifier or code that characterizes one of its properties or attributes.
-
E.
isServedByCode
chosen
Indicates that a service, resource, or item is provided, delivered, or fulfilled through a specific code.
- 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_69f34920aa4081908d8fb0277414b911 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69ff519b65f081909902ba83b775ef85 |
completed | May 9, 2026, 3:24 p.m. |
| PD | Predicate disambiguation | batch_69ff506fccdc8190bd93269589040aed |
completed | May 9, 2026, 3:19 p.m. |
Created at: May 1, 2026, 12:59 a.m.