Triple
T23155239
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kanban (software development) |
E578419
|
entity |
| Predicate | boardColumn |
P65672
|
FINISHED |
| Object | To Do |
—
|
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: To Do | Statement: [Kanban (software development), boardColumn, To Do]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: boardColumn Context triple: [Kanban (software development), boardColumn, To Do]
-
A.
column
chosen
Indicates a vertical structural element that supports or separates parts within a larger construction or arrangement.
-
B.
board
Indicates that an agent gets onto or into a vehicle, vessel, or craft in order to travel or be transported.
-
C.
currentStandingColumns
Indicates that certain columns are presently active, visible, or in use within a given context or layout.
-
D.
centralColumnHeight
Indicates that one entity specifies or measures the height of a central column relative to a structure or reference frame.
-
E.
boardProperties
Indicates a relationship where specific attributes or characteristics are assigned to or associated with a board.
- 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_69e245fb8de081908f0eba7b5fd75bc4 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f18efca1f081908ff1c34ba25f40c3 |
completed | April 29, 2026, 4:54 a.m. |
| PD | Predicate disambiguation | batch_69ef89ff76808190808ee4ad9dea776b |
completed | April 27, 2026, 4:08 p.m. |
Created at: April 17, 2026, 4:01 p.m.