Triple
T37447478
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fiuggi Congress 1995 |
E930586
|
entity |
| Predicate | associatedPartyAfter |
P20464
|
FINISHED |
| Object | National Alliance |
E96450
|
NE 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: National Alliance | Statement: [Fiuggi Congress 1995, associatedPartyAfter, National Alliance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedPartyAfter Context triple: [Fiuggi Congress 1995, associatedPartyAfter, National Alliance]
-
A.
replacedParty
Indicates that one entity has been substituted for or taken the place of another entity in a given role, position, or context.
-
B.
associatedThrough
Indicates that two entities are connected or related to each other by means of a specified intermediary, context, or linkage.
-
C.
resultingParty
Indicates the party that emerges as the outcome or beneficiary of a given event, process, or transaction.
-
D.
otherSignificantParty
Indicates that an entity has another important associated party, such as a key counterpart, partner, or involved participant in a relationship or transaction.
-
E.
participatingParty
chosen
Indicates that an entity is involved as a participant in a particular event, activity, or transaction.
- F. None of above.
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_69f76ec0b9488190b7a4fae632bd1d2f |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a409ef570d08190a937a23dab2b04b1 |
completed | June 28, 2026, 4:11 a.m. |
| PD | Predicate disambiguation | batch_6a037a13a1308190a202df66f4781855 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:17 p.m.