Triple
T34348187
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Polish parliamentary election, 1997 |
E881493
|
entity |
| Predicate | mainWinningAllianceAbbreviation |
P112542
|
FINISHED |
| Object | AWS |
—
|
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: AWS | Statement: [Polish parliamentary election, 1997, mainWinningAllianceAbbreviation, AWS]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainWinningAllianceAbbreviation Context triple: [Polish parliamentary election, 1997, mainWinningAllianceAbbreviation, AWS]
-
A.
mainWinningAlliance
Indicates that the referenced alliance is the primary winner in a competitive event or contest.
-
B.
winnerAbbreviation
chosen
Indicates the abbreviated form or short code used to represent the winner in a given context or event.
-
C.
winningTeamLeague
Indicates that a team is the champion or first-place finisher of a particular league in a given season or competition.
-
D.
allianceName
Indicates the designated name or title assigned to an alliance between entities.
-
E.
federationAbbreviation
Indicates that one entity is the standard short-form or abbreviated designation of a federation associated with another 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_69f349bc55e881908c8e338ef76b0043 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f717836f0c8190b4a397bbac37dd09 |
completed | May 3, 2026, 9:38 a.m. |
| PD | Predicate disambiguation | batch_69f7127a2ff08190b77d00963c9df621 |
completed | May 3, 2026, 9:16 a.m. |
Created at: May 1, 2026, 1:58 a.m.