Triple
T14539325
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ONC RPC |
E341127
|
entity |
| Predicate | serviceDiscoveryMechanism |
P7311
|
FINISHED |
| Object | portmapper |
—
|
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: portmapper | Statement: [ONC RPC, serviceDiscoveryMechanism, portmapper]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: serviceDiscoveryMechanism Context triple: [ONC RPC, serviceDiscoveryMechanism, portmapper]
-
A.
serviceLocation
Indicates the place or address where a service is provided, performed, or made available to the relevant party.
-
B.
discoveryMethod
chosen
Indicates the process, technique, or approach by which something was found, detected, or identified.
-
C.
ringDiscovery
Indicates that an entity discovers, finds, or becomes aware of a particular ring.
-
D.
serviceWith
Indicates that one entity provides or is associated with a particular service offered to or used by another entity.
-
E.
supportedDiscoveryOf
Indicates that one entity aided, enabled, or contributed to another entity’s act of discovering something.
- 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_69d822dac79c8190a84a073f3cbaced5 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb1bd0dd4819094c8b2f2aa6b1c5e |
completed | April 14, 2026, 9:29 p.m. |
| PD | Predicate disambiguation | batch_69de5c546c7081909e27d504ec360c5c |
completed | April 14, 2026, 3:25 p.m. |
Created at: April 10, 2026, 1:22 a.m.