Triple
T548235
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Australia/Brisbane |
E12778
|
entity |
| Predicate | networkProtocolUsage |
P3331
|
FINISHED |
| Object | used in POSIX systems |
—
|
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: used in POSIX systems | Statement: [Australia/Brisbane, networkProtocolUsage, used in POSIX systems]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: networkProtocolUsage Context triple: [Australia/Brisbane, networkProtocolUsage, used in POSIX systems]
-
A.
transportProtocol
Indicates the communication protocol used to transport data between entities in a networked interaction.
-
B.
networkType
Indicates the category or kind of network associated with or used by an entity (e.g., wired, wireless, virtual, or specific protocol-based networks).
-
C.
usedInProtocol
chosen
Indicates that something (e.g., a method, component, or resource) is employed as part of the steps or structure of a specific protocol.
-
D.
network
Indicates that one entity is connected to or interacts with another through a system of relationships, communication, or information exchange.
-
E.
protocolNumber
Indicates the specific identifying number assigned to a protocol that governs or documents an interaction, process, or agreement between entities.
- 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_69a49334226c81908b0ea1689ef6aa3f |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a49900895c819092a131c185a758bf |
completed | March 1, 2026, 7:52 p.m. |
| PD | Predicate disambiguation | batch_69a494b957988190bc269e372df2f0b2 |
completed | March 1, 2026, 7:34 p.m. |
Created at: March 1, 2026, 7:32 p.m.