Triple
T29659879
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jubilee Alliance |
E750375
|
entity |
| Predicate | promisedPolicy |
P162828
|
FINISHED |
| Object | infrastructure development |
—
|
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: infrastructure development | Statement: [Jubilee Alliance, promisedPolicy, infrastructure development]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: promisedPolicy Context triple: [Jubilee Alliance, promisedPolicy, infrastructure development]
-
A.
endedPolicy
Indicates that a previously active policy has been brought to an end or terminated.
-
B.
promisedFeature
chosen
Indicates that one entity has committed to providing or implementing a specific feature for another entity.
-
C.
compromisePolicy
Indicates that an entity weakens, violates, or undermines a policy, reducing its intended effectiveness or integrity.
-
D.
establishedPolicy
Indicates that a policy has been formally created, adopted, and put into effect as a guiding rule or standard.
-
E.
implementedPolicy
Indicates that a particular policy has been put into effect or carried out by an entity.
- 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_69f0d6226fe881908819197c9ef9ee04 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f674e06c9481909ed0ea736408f0d7 |
completed | May 2, 2026, 10:04 p.m. |
| PD | Predicate disambiguation | batch_69f673c4abec8190bc2379e66f4af0a9 |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 28, 2026, 6:57 p.m.