Triple
T27572221
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TRILL |
E696065
|
entity |
| Predicate | forwardingElement |
P122404
|
FINISHED |
| Object | Routing Bridge |
—
|
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 Bridge | Statement: [TRILL, forwardingElement, Routing Bridge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: forwardingElement Context triple: [TRILL, forwardingElement, Routing Bridge]
-
A.
forwardingMethod
Indicates the method or mechanism by which something (such as a message, request, or item) is forwarded from one point or entity to another.
-
B.
forwardBase
Indicates that one location or entity serves as an advanced or frontline operational base relative to another.
-
C.
forward
chosen
Indicates that one entity sends, directs, or passes something on to another entity, typically along a path or sequence.
-
D.
requiresFollowingElement
Indicates that one element must be immediately followed by a specific subsequent element in order to be valid or complete.
-
E.
isDestinationFor
Indicates that one entity serves as the endpoint or target location that another entity is intended to reach or be directed toward.
- 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_69f6359e3d3c81909814e2f0a7fb0ea9 |
completed | May 2, 2026, 5:34 p.m. |
| PD | Predicate disambiguation | batch_69f631871c888190bf29466fe4254e51 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 27, 2026, 1:43 p.m.