Triple
T25038409
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Power Jets Ltd |
E627042
|
entity |
| Predicate | usedFundingFrom |
P159409
|
FINISHED |
| Object | Air Ministry |
—
|
NE NERFINISHED |
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: Air Ministry | Statement: [Power Jets Ltd, usedFundingFrom, Air Ministry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedFundingFrom Context triple: [Power Jets Ltd, usedFundingFrom, Air Ministry]
-
A.
usedFund
Indicates that one entity expended or applied a particular fund or financial resource for some purpose.
-
B.
usedFeederFunds
Indicates that an entity employed feeder funds as intermediary investment vehicles to channel capital into another fund or investment structure.
-
C.
usedFundingMethods
Indicates that an entity employed specific funding methods to finance an activity, project, or operation.
-
D.
permittedFundingFrom
Indicates that providing financial resources from one entity to another is allowed under specified rules or conditions.
-
E.
fundingContext
Indicates the circumstances, purpose, or conditions under which funding is provided or used in a given relationship or action.
- 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_69e2ff2a2c088190be513727ee8bfe78 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f584f07b648190aee894c1d5320bc3 |
completed | May 2, 2026, 5 a.m. |
| PD | Predicate disambiguation | batch_69f4a0edd10c81908a052ab864d57c54 |
completed | May 1, 2026, 12:47 p.m. |
| PDg | Predicate description generation | batch_69f55e497fa081909bc59a7b92c5df59 |
completed | May 2, 2026, 2:15 a.m. |
Created at: April 18, 2026, 6:08 a.m.