Triple
T8470834
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Name Binding Protocol |
E200275
|
entity |
| Predicate | usesAddressingScheme |
P1216
|
FINISHED |
| Object | AppleTalk network address |
—
|
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: AppleTalk network address | Statement: [Name Binding Protocol, usesAddressingScheme, AppleTalk network address]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesAddressingScheme Context triple: [Name Binding Protocol, usesAddressingScheme, AppleTalk network address]
-
A.
usesAddressingSystem
chosen
Indicates that one entity employs or applies a particular addressing system associated with another entity.
-
B.
hasAddress
Indicates that an entity is associated with a specific address or location.
-
C.
addressingMechanism
Indicates the method or system used to identify, locate, or reference a target within a larger space, network, or structure.
-
D.
hasDirectionScheme
Indicates that an entity is associated with or governed by a particular scheme or system for defining directions.
-
E.
canAddress
Indicates that one entity has the ability or permission to direct communication, action, or service toward another entity.
- 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_69ca831a4f348190bfdd09250e86ae35 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe4f234c481909534de6fd702f4cf |
completed | March 31, 2026, 3:14 p.m. |
| PD | Predicate disambiguation | batch_69cbd10072cc819084be1ed9ac7ebe9d |
completed | March 31, 2026, 1:49 p.m. |
Created at: March 30, 2026, 6:11 p.m.