Triple
T23155595
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dave Thomas |
E578426
|
entity |
| Predicate | roleInAgileManifesto |
P151134
|
FINISHED |
| Object | original signatory |
—
|
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: original signatory | Statement: [Dave Thomas, roleInAgileManifesto, original signatory]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInAgileManifesto Context triple: [Dave Thomas, roleInAgileManifesto, original signatory]
-
A.
roleInToolchain
Indicates that an entity serves a specific function or position within a larger sequence of tools or processes in a toolchain.
-
B.
roleInTheory
Indicates the specific function, position, or contribution that an entity has within a particular theory or theoretical framework.
-
C.
roleInProjectLifecycle
Indicates the specific function or responsibility an entity has at a particular stage of a project's lifecycle.
-
D.
roleInCommandStructure
Indicates that one entity holds a specific position or function within the hierarchical command structure of another entity or organization.
-
E.
portfolioRole
Indicates the specific function, capacity, or position an entity holds within a portfolio or collection of assets.
- 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_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. |
| PDg | Predicate description generation | batch_69ef9b7494f4819088ae59ea3d0ae8ab |
completed | April 27, 2026, 5:23 p.m. |
Created at: April 17, 2026, 4:01 p.m.