Triple
T8154254
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baldrick |
E190405
|
entity |
| Predicate | planningSkill |
P80852
|
FINISHED |
| Object | notoriously poor |
—
|
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: notoriously poor | Statement: [Baldrick, planningSkill, notoriously poor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: planningSkill Context triple: [Baldrick, planningSkill, notoriously poor]
-
A.
planning
Indicates that an entity is engaged in organizing or devising a future action, event, or course of behavior involving another entity or entities.
-
B.
planningProcess
Indicates a relationship where an entity is engaged in or associated with the structured activity of defining goals, strategies, and steps to achieve a desired outcome.
-
C.
planningResponse
Indicates that an agent formulates, selects, or communicates a course of action or plan in response to a given situation, goal, or request.
-
D.
planner
Indicates that an entity is responsible for organizing, scheduling, or coordinating activities, tasks, or resources.
-
E.
plannedWith
Indicates that an entity created or arranged a plan in collaboration or coordination with another entity.
- 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_69ca82bfeb6481909d07b91b5cf69f59 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb44d566b08190a6bb672f9c368806 |
completed | March 31, 2026, 3:51 a.m. |
| PD | Predicate disambiguation | batch_69cb36a0847c8190af9038aef78319b3 |
completed | March 31, 2026, 2:51 a.m. |
| PDg | Predicate description generation | batch_69cb39ba412881908a053e88f29a9588 |
completed | March 31, 2026, 3:04 a.m. |
Created at: March 30, 2026, 5:37 p.m.