Triple
T7936452
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Domino Router |
E184298
|
entity |
| Predicate | taskName |
P79891
|
FINISHED |
| Object | ROUTER |
—
|
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: ROUTER | Statement: [Domino Router, taskName, ROUTER]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: taskName Context triple: [Domino Router, taskName, ROUTER]
-
A.
taskType
Indicates the specific category or kind of task an action or assignment belongs to within a broader set of tasks.
-
B.
taskForce
Indicates a collaborative relationship in which multiple entities are formally grouped to work together as a specialized team on a specific task or mission.
-
C.
canTask
Indicates that an entity has the ability or permission to perform a specified task.
-
D.
workingName
Indicates that one entity serves as a temporary, provisional, or informal name currently used for another entity.
-
E.
missionName
Indicates the designated title or label assigned to a specific mission or operation.
- 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_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. |
| PDg | Predicate description generation | batch_69caf7882b048190baa333af9f698590 |
completed | March 30, 2026, 10:22 p.m. |
Created at: March 30, 2026, 5:08 p.m.