Triple
T29030703
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NBP Broadcast |
E737719
|
entity |
| Predicate | usedInNetworkArchitecture |
P185306
|
FINISHED |
| Object | AppleTalk |
—
|
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: AppleTalk | Statement: [NBP Broadcast, usedInNetworkArchitecture, AppleTalk]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInNetworkArchitecture Context triple: [NBP Broadcast, usedInNetworkArchitecture, AppleTalk]
-
A.
usedByNetwork
Indicates that something is utilized or operated by a particular network.
-
B.
usedInTelecommunications
Indicates that something is employed as a component, tool, or method within telecommunications systems or processes.
-
C.
inNetwork
Indicates that one entity is within the same defined network, system, or coverage group as another entity, such that network-based interactions or benefits apply between them.
-
D.
usedInProtocol
Indicates that something (e.g., a method, component, or resource) is employed as part of the steps or structure of a specific protocol.
-
E.
usedByNetworkFunction
Indicates that a resource, component, or service is utilized or consumed by a specific network function.
- 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_69f077ef00fc81909325f084ad37c035 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f7be53890081909b1d93f30a8f31c6 |
completed | May 3, 2026, 9:29 p.m. |
| PD | Predicate disambiguation | batch_69f7bccacbac8190978976324c67db28 |
completed | May 3, 2026, 9:23 p.m. |
| PDg | Predicate description generation | batch_69f7be520f148190ba200bf3dbf40656 |
completed | May 3, 2026, 9:29 p.m. |
Created at: April 28, 2026, 9:55 a.m.