Triple
T17391228
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Israeli legislative election, 1959 |
E422826
|
entity |
| Predicate | arabSatelliteListsSeats |
P126401
|
FINISHED |
| Object | 4 |
—
|
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: 4 | Statement: [Israeli legislative election, 1959, arabSatelliteListsSeats, 4]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: arabSatelliteListsSeats Context triple: [Israeli legislative election, 1959, arabSatelliteListsSeats, 4]
-
A.
ArabSatelliteListsSeatsWon
chosen
Indicates the number of seats won by an Arab satellite (e.g., party or list) in an election or representative body.
-
B.
retrievedSatellite
Indicates that an entity has successfully recovered or brought back a satellite from a prior location or state.
-
C.
deployedSatellite
Indicates that one entity has placed another entity into orbit or operational status as a satellite.
-
D.
relatedSpacecraft
Indicates that there is an association or connection between two spacecraft, such as shared mission, design, origin, or operational relationship.
-
E.
plannedSatellites
Indicates that certain satellites are intended or scheduled to be launched, deployed, or put into operation in association with a given entity or context.
- 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.