Triple
T29304977
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AppleTalk addressing |
E743066
|
entity |
| Predicate | fullNameOfRTMP |
P167417
|
FINISHED |
| Object | Routing Table Maintenance 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: Routing Table Maintenance Protocol | Statement: [AppleTalk addressing, fullNameOfRTMP, Routing Table Maintenance Protocol]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fullNameOfRTMP Context triple: [AppleTalk addressing, fullNameOfRTMP, Routing Table Maintenance Protocol]
-
A.
runtimeName
Indicates the name of the runtime environment or platform under which an entity (such as a program or process) is executed.
-
B.
fullNameOfDDP
Indicates that one entity is the full, explicit name (e.g., complete designation) of a given DDP (Data/Delivery/Distribution Point or similarly defined DDP entity).
-
C.
rootName
Indicates that the referenced node serves as the primary or top-level root in a hierarchical structure or dependency tree.
-
D.
terminalName
Indicates the name or label assigned to a specific terminal or endpoint within a system or network.
-
E.
programFullName
Indicates the complete, official name of a program as opposed to an abbreviation or short title.
- 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_69f66a6468ec8190a43ed6cd8c797f42 |
completed | May 2, 2026, 9:19 p.m. |
| PD | Predicate disambiguation | batch_69f6659b62fc8190b21555d0ba54db2d |
completed | May 2, 2026, 8:59 p.m. |
| PDg | Predicate description generation | batch_69f6691da93081909deaf680614fc900 |
completed | May 2, 2026, 9:14 p.m. |
Created at: April 28, 2026, 1:12 p.m.