Triple
T29304971
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AppleTalk addressing |
E743066
|
entity |
| Predicate | usedByHigherLevelProtocols |
P3331
|
FINISHED |
| Object | AppleTalk Filing Protocol |
—
|
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 Filing Protocol | Statement: [AppleTalk addressing, usedByHigherLevelProtocols, AppleTalk Filing Protocol]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedByHigherLevelProtocols Context triple: [AppleTalk addressing, usedByHigherLevelProtocols, AppleTalk Filing Protocol]
-
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.
mayUseProtocol
Indicates that an entity is permitted or authorized to employ a specified protocol for communication or operation.
-
C.
usesProtocolSuite
Indicates that one entity operates or communicates by employing the set of communication protocols defined by another entity’s protocol suite.
-
D.
supportedProtocol
Indicates that one entity is compatible with, implements, or can operate using a specified communication or interaction protocol.
-
E.
usesIPProtocol
Indicates that one entity communicates or operates using a specific IP (Internet Protocol) version 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_69f09123ed9881909f351f7541933f5e |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69f727afd5d88190ad48735cd1b32787 |
completed | May 3, 2026, 10:47 a.m. |
| PD | Predicate disambiguation | batch_69f72737c42c8190a3f781a5e98868ff |
completed | May 3, 2026, 10:45 a.m. |
Created at: April 28, 2026, 1:12 p.m.