Triple
T7427802
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EIGRP |
E171411
|
entity |
| Predicate | routingDomainScope |
P76949
|
FINISHED |
| Object | intra-domain |
—
|
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: intra-domain | Statement: [EIGRP, routingDomainScope, intra-domain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: routingDomainScope Context triple: [EIGRP, routingDomainScope, intra-domain]
-
A.
routingDomainType
Indicates the classification or category of routing domain associated with a given routing configuration or relationship.
-
B.
locationScope
Indicates the specific geographic or spatial area within which a given relationship, condition, or action is considered valid or applicable.
-
C.
transportDomain
Indicates a relationship where an entity operates or functions within the domain or context of transportation activities or systems.
-
D.
regulatoryDomain
Indicates that one entity defines or governs the rules, policies, or constraints under which another entity must operate.
-
E.
organizationalScope
Indicates the range or extent of responsibility, authority, or applicability that an action, policy, or relationship has within an organization or its sub-units.
- 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_69c68a63491881909281f73d4d5643bf |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f306bfe481909f99f6792de95ffc |
completed | March 27, 2026, 9:13 p.m. |
| PD | Predicate disambiguation | batch_69c6f03648d08190b862d07fef71210c |
completed | March 27, 2026, 9:01 p.m. |
| PDg | Predicate description generation | batch_69c6f1ee5ab8819091082324f2dc3b8c |
completed | March 27, 2026, 9:09 p.m. |
Created at: March 27, 2026, 3:12 p.m.