Triple
T27572442
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | L3Out |
E696069
|
entity |
| Predicate | definedInTerminology |
P173342
|
FINISHED |
| Object | External Routed Network |
—
|
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: External Routed Network | Statement: [L3Out, definedInTerminology, External Routed Network]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: definedInTerminology Context triple: [L3Out, definedInTerminology, External Routed Network]
-
A.
definedInTerm
chosen
Indicates that one entity is defined or formally specified within the scope or content of a particular term.
-
B.
usesTerminologyFrom
Indicates that one entity adopts or incorporates the specialized terms or vocabulary originating from another entity or source.
-
C.
definedInField
Indicates that something (such as a concept, method, or element) is formally specified, declared, or established within a particular field, domain, or area of study.
-
D.
definedInPart
Indicates that something is specified, described, or formally established within a particular part or section of a larger whole.
-
E.
defined
Indicates that one entity specifies, explains, or establishes the meaning, scope, or identity of another entity.
- F. None of above.
Provenance (3 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_69ef53891af88190a193c5e2a1dac9b1 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f70e8755a48190931eaa77946f9460 |
completed | May 3, 2026, 8:59 a.m. |
| PD | Predicate disambiguation | batch_69f70abc00848190a1c3f495ef6c8dc6 |
completed | May 3, 2026, 8:43 a.m. |
Created at: April 27, 2026, 1:44 p.m.