Triple
T29659891
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jubilee Alliance |
E750375
|
entity |
| Predicate | mergedPartiesInto |
P77
|
FINISHED |
| Object | The National Alliance |
—
|
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: The National Alliance | Statement: [Jubilee Alliance, mergedPartiesInto, The National Alliance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mergedPartiesInto Context triple: [Jubilee Alliance, mergedPartiesInto, The National Alliance]
-
A.
compactParties
Indicates that the referenced parties are participants in, or signatories to, the same compact or formal agreement.
-
B.
mainParties
Indicates the primary entities that are directly and centrally involved in a given relationship, event, or agreement.
-
C.
mergedInto
chosen
Indicates that one entity has been combined with and absorbed into another entity, ceasing to exist as a separate unit.
-
D.
mergedBy
Indicates that one entity is combined or integrated into another entity through the action or decision of a specific agent.
-
E.
mergedOrReorganized
Indicates that one entity has combined with or been structurally reorganized into another entity, resulting in a changed or unified organizational form.
- 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_69f67257b0448190a13011af81c81449 |
completed | May 2, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69f66ec5bf508190ad088b89455252bd |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 28, 2026, 6:57 p.m.