Triple
T17391223
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Israeli legislative election, 1959 |
E422826
|
entity |
| Predicate | mapamSeats |
P124894
|
FINISHED |
| Object | 9 |
—
|
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: 9 | Statement: [Israeli legislative election, 1959, mapamSeats, 9]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mapamSeats Context triple: [Israeli legislative election, 1959, mapamSeats, 9]
-
A.
seatCountOfMapam
chosen
Indicates the number of seats associated with Mapam in a given legislative or representative body.
-
B.
mapsAs
Indicates that one entity serves as a mapping or correspondence to another, typically translating or associating elements from one domain or representation to another.
-
C.
mapNumber
Indicates a correspondence where each element in one set or collection is assigned a specific numeric value in another set or domain.
-
D.
mapsFrom
Indicates that one entity is derived, transformed, or constructed based on data, structure, or content originating from another entity.
-
E.
mapSystem
Indicates a relationship where one system is associated with or represented by a specific map or mapping framework.
- 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_69d889d710288190bf0f4762801fefae |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e43aba5398819096846bdeefde0788 |
completed | April 19, 2026, 2:15 a.m. |
| PD | Predicate disambiguation | batch_69e3b02ac8688190a7182f1b2151d721 |
completed | April 18, 2026, 4:24 p.m. |
Created at: April 10, 2026, 5:45 a.m.