Triple
T21802549
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IIH PDU |
E538271
|
entity |
| Predicate | roleInIS-IS |
P145699
|
FINISHED |
| Object | discovers neighbors on a link |
—
|
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: discovers neighbors on a link | Statement: [IIH PDU, roleInIS-IS, discovers neighbors on a link]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInIS-IS Context triple: [IIH PDU, roleInIS-IS, discovers neighbors on a link]
-
A.
roleInProtocolStack
Indicates the specific function or position an entity occupies within a layered communication or protocol stack.
-
B.
ICAORole
Indicates a role or function that an entity holds within the context of ICAO (International Civil Aviation Organization) activities, structures, or regulations.
-
C.
roleIn3GPP
Indicates that an entity holds a specific role or function within the context of 3GPP (Third Generation Partnership Project) standards or activities.
-
D.
roleInOperation
Indicates that an entity holds a specific function, duty, or position within a particular operation or activity.
-
E.
roleInCluster
Indicates the specific function or position an entity holds within a defined group or cluster of related entities.
- 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_69e0c4733f4081909a86622e7e6d15d2 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f0780062688190a6c3a2a0364f0f77 |
completed | April 28, 2026, 9:04 a.m. |
| PD | Predicate disambiguation | batch_69e6be751ce881909badced245ef76c7 |
completed | April 21, 2026, 12:01 a.m. |
| PDg | Predicate description generation | batch_69e6c3a2898881909748935cf92f898c |
completed | April 21, 2026, 12:24 a.m. |
Created at: April 16, 2026, 6:53 p.m.