Triple
T27638947
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bitcoin testnet |
E696536
|
entity |
| Predicate | defaultRPCHTTPPort |
P2552
|
FINISHED |
| Object | 18332 |
—
|
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: 18332 | Statement: [Bitcoin testnet, defaultRPCHTTPPort, 18332]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: defaultRPCHTTPPort Context triple: [Bitcoin testnet, defaultRPCHTTPPort, 18332]
-
A.
defaultPort
chosen
Indicates that one entity serves as the standard or preconfigured communication port used by another entity unless explicitly overridden.
-
B.
defaultPortSecure
Indicates that the default network port for a service or application is configured to use secure communication (e.g., encrypted or authenticated).
-
C.
typicalPort
Indicates that a specified port is commonly or normally used for a given service, protocol, or application.
-
D.
portNumber
Indicates the specific communication port assigned to a network connection, service, or endpoint.
-
E.
registeredPort
Indicates that a specific network port number has been officially assigned and recorded for use by a particular service or protocol.
- 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_69ef5909f3848190805f35b76833e722 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f65a6c900881908f18b61273d7bf8d |
completed | May 2, 2026, 8:11 p.m. |
| PD | Predicate disambiguation | batch_69f659ce58408190ba9e007b4810d4d0 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 27, 2026, 2:25 p.m.