Triple
T17906503
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | the Eds |
E447714
|
entity |
| Predicate | typicalOutcomeOfSchemes |
P102601
|
FINISHED |
| Object | failure |
—
|
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: failure | Statement: [the Eds, typicalOutcomeOfSchemes, failure]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalOutcomeOfSchemes Context triple: [the Eds, typicalOutcomeOfSchemes, failure]
-
A.
planOutcome
chosen
Indicates the result or consequence that is expected or produced by a given plan.
-
B.
reformOutcome
Indicates the result or consequence produced by a particular reform or change initiative.
-
C.
relatedGrantScheme
Indicates that there is an associated grant scheme that is relevant or linked to the subject entity.
-
D.
governsOutcome
Indicates that one entity has decisive control or influence over the result or consequence affecting another entity.
-
E.
preDeterminedOutcomes
Indicates that the outcomes of an event or process are fixed in advance and not influenced by subsequent actions or conditions.
- 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_69d8b9f6d394819082a6d69fd1e23d2f |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e49e9c7f54819088c6d2ce7bbea073 |
completed | April 19, 2026, 9:21 a.m. |
| PD | Predicate disambiguation | batch_69e3d8ec2f6881909d7f54b878cbed37 |
completed | April 18, 2026, 7:18 p.m. |
Created at: April 10, 2026, 10:19 a.m.