Triple
T27730325
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RPC over HTTP |
E697414
|
entity |
| Predicate | tunnelsProtocol |
P163116
|
FINISHED |
| Object | Microsoft Remote Procedure Call |
—
|
NE NERFINISHED |
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: Microsoft Remote Procedure Call | Statement: [RPC over HTTP, tunnelsProtocol, Microsoft Remote Procedure Call]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tunnelsProtocol Context triple: [RPC over HTTP, tunnelsProtocol, Microsoft Remote Procedure Call]
-
A.
tunnelType
Indicates the specific kind or classification of a tunnel associated with an entity.
-
B.
tunnels
Indicates that one entity passes through, under, or within another entity via a tunnel-like passage or structure.
-
C.
tunnelUse
Indicates that one entity makes use of or passes through a tunnel associated with another entity.
-
D.
numberOfTunnels
Indicates the quantity of tunnels associated with or passing through a given entity or location.
-
E.
tunnelOperationMode
Indicates the specific operational state or mode in which a tunnel system or tunnel-related process is currently functioning.
- F. None of above. chosen
Provenance (4 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_69ef590c3e288190ad54d2465af8ca4e |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f6369b658c8190bc6d697b9a4d5c03 |
completed | May 2, 2026, 5:38 p.m. |
| PD | Predicate disambiguation | batch_69f63188e7408190af8ce8b93d128c63 |
completed | May 2, 2026, 5:16 p.m. |
| PDg | Predicate description generation | batch_69f6352df6148190bc10772cd40bd7b3 |
completed | May 2, 2026, 5:32 p.m. |
Created at: April 27, 2026, 3:11 p.m.