Triple
T7936453
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Domino Router |
E184298
|
entity |
| Predicate | canRoute |
P64268
|
FINISHED |
| Object | Notes mail |
—
|
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: Notes mail | Statement: [Domino Router, canRoute, Notes mail]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canRoute Context triple: [Domino Router, canRoute, Notes mail]
-
A.
mayRouteTo
chosen
Indicates that one entity is permitted or able to direct, forward, or transfer something (such as data, traffic, or requests) to another entity.
-
B.
hasRoute
Indicates that there exists a path or connection enabling travel or communication from one entity to another.
-
C.
isRouteFor
Indicates that one entity serves as a path, course, or channel used for traveling, transporting, or connecting to another entity.
-
D.
routeMayInclude
Indicates that a given route can optionally pass through, contain, or involve a specified segment, location, or element as part of its path.
-
E.
supportsRouting
Indicates that one entity provides the capability to determine and direct paths or routes for another entity’s traffic, requests, or messages.
- 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_69ca8290c21c8190906a5ca6fe2b03c4 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb3aede3cc81908b0d3b54e68997b9 |
completed | March 31, 2026, 3:09 a.m. |
| PD | Predicate disambiguation | batch_69cae9335f288190ba96781fd6576a2b |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 5:08 p.m.