Triple
T27638946
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bitcoin testnet |
E696536
|
entity |
| Predicate | defaultP2PPort |
P2552
|
FINISHED |
| Object | 18333 |
—
|
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: 18333 | Statement: [Bitcoin testnet, defaultP2PPort, 18333]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: defaultP2PPort Context triple: [Bitcoin testnet, defaultP2PPort, 18333]
-
A.
defaultPort
chosen
Indicates that one entity serves as the standard or preconfigured communication port used by another entity unless explicitly overridden.
-
B.
portNumber
Indicates the specific communication port assigned to a network connection, service, or endpoint.
-
C.
typicalPort
Indicates that a specified port is commonly or normally used for a given service, protocol, or application.
-
D.
dynamicPortRange
Indicates that a system or service uses a configurable range of network ports that can be dynamically allocated rather than fixed to a single port.
-
E.
exportPort
Indicates the port or harbor from which goods, resources, or data are sent out from one location or entity to another.
- 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_69f65876c52c8190bc889c7a67bd07f3 |
completed | May 2, 2026, 8:03 p.m. |
| PD | Predicate disambiguation | batch_69f6575d89788190aca478e4aea05a65 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 27, 2026, 2:25 p.m.