Triple
T21128441
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Capital Investment Grants |
E520619
|
entity |
| Predicate | projectPhaseSupported |
P114525
|
FINISHED |
| Object | engineering |
—
|
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: engineering | Statement: [Capital Investment Grants, projectPhaseSupported, engineering]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: projectPhaseSupported Context triple: [Capital Investment Grants, projectPhaseSupported, engineering]
-
A.
programPhase
Indicates the specific stage or phase within a broader program or process that an entity is currently associated with.
-
B.
developmentPhaseName
chosen
Indicates the specific stage or phase name within a broader development process or lifecycle.
-
C.
applicationPhase
Indicates the specific stage or step an application is currently in within a broader application process.
-
D.
supportsProjectsIn
Indicates that one entity provides assistance, resources, or backing for projects occurring within or associated with another entity.
-
E.
supportsProject
Indicates that one entity provides assistance, resources, or endorsement to help another entity’s project succeed.
- 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_69e0b50a623881909c0bbaf4f2c055e7 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e7223a7a588190a01a66921b79b98b |
completed | April 21, 2026, 7:07 a.m. |
| PD | Predicate disambiguation | batch_69e5f5ed6c8c8190b31092a5d4c3de5d |
completed | April 20, 2026, 9:46 a.m. |
Created at: April 16, 2026, 2:56 p.m.