Triple
T29304969
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AppleTalk addressing |
E743066
|
entity |
| Predicate | fullNameOfDDP |
P166948
|
FINISHED |
| Object | Datagram Delivery 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: Datagram Delivery Protocol | Statement: [AppleTalk addressing, fullNameOfDDP, Datagram Delivery Protocol]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fullNameOfDDP Context triple: [AppleTalk addressing, fullNameOfDDP, Datagram Delivery Protocol]
-
A.
fullName
Indicates that an entity has a complete personal name, typically combining given name(s) and family name into a single string.
-
B.
displayName
Indicates the human-readable name or label that is shown to users when presenting an entity.
-
C.
FIELDSFullName
Indicates that one entity’s full name is recorded as a field or attribute associated with another entity.
-
D.
CDTFullName
Indicates that one entity is the complete, expanded name (full name) corresponding to another entity.
-
E.
fullGivenNameOf
Indicates that one entity is the complete, formal given name corresponding to another entity (such as a person or identifier).
- 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_69f09123ed9881909f351f7541933f5e |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69f665a5724c8190b3c31ea61745a426 |
completed | May 2, 2026, 8:59 p.m. |
| PD | Predicate disambiguation | batch_69f663362c008190a22afed262f1e426 |
completed | May 2, 2026, 8:48 p.m. |
| PDg | Predicate description generation | batch_69f6645a615481909b53d94512ecbaf1 |
completed | May 2, 2026, 8:53 p.m. |
Created at: April 28, 2026, 1:12 p.m.