Triple
T30152516
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Resource Public Key Infrastructure |
E766430
|
entity |
| Predicate | ROAFullName |
P168487
|
FINISHED |
| Object | Route Origin Authorization |
—
|
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: Route Origin Authorization | Statement: [Resource Public Key Infrastructure, ROAFullName, Route Origin Authorization]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ROAFullName Context triple: [Resource Public Key Infrastructure, ROAFullName, Route Origin Authorization]
-
A.
commanderFullName
Indicates that the predicate specifies the complete personal name of the commander associated with an entity.
-
B.
RANName
Indicates that an entity has a specific Radio Access Network (RAN) name assigned to it.
-
C.
FIELDSFullName
Indicates that one entity’s full name is recorded as a field or attribute associated with another entity.
-
D.
firstOfficialName
Indicates the original or primary official name formally assigned to an entity before any subsequent name changes or alternatives.
-
E.
fullName
Indicates that an entity has a complete personal name, typically combining given name(s) and family name into a single string.
- 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_69f22479cd088190ab4c6f3fce39d1c5 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f67ed4df5081908d1431e3a1a1fb0e |
completed | May 2, 2026, 10:46 p.m. |
| PD | Predicate disambiguation | batch_69f673c7a4588190837854f3ef61e6bf |
completed | May 2, 2026, 9:59 p.m. |
| PDg | Predicate description generation | batch_69f6749f205c81909d1aacf462912eee |
completed | May 2, 2026, 10:03 p.m. |
Created at: April 29, 2026, 7:20 p.m.