Triple
T29304947
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AppleTalk addressing |
E743066
|
entity |
| Predicate | usedInProtocolSuite |
P3331
|
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: [AppleTalk addressing, usedInProtocolSuite, AppleTalk]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInProtocolSuite Context triple: [AppleTalk addressing, usedInProtocolSuite, AppleTalk]
-
A.
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.
-
B.
usesProtocolSuite
Indicates that one entity operates or communicates by employing the set of communication protocols defined by another entity’s protocol suite.
-
C.
mayUseProtocol
Indicates that an entity is permitted or authorized to employ a specified protocol for communication or operation.
-
D.
usedInInterface
Indicates that something is employed or incorporated as a component or element within a user interface.
-
E.
usedInTelecommunicationsStandardization
Indicates that something is employed or plays a role within the processes, documents, or frameworks of telecommunications standardization.
- 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_69f09123ed9881909f351f7541933f5e |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69fbaebc8f2c8190b94f1b4a3ec92e8c |
completed | May 6, 2026, 9:12 p.m. |
| PD | Predicate disambiguation | batch_69fbadf1e6008190a71bbd196ba06844 |
completed | May 6, 2026, 9:09 p.m. |
Created at: April 28, 2026, 1:12 p.m.