Triple
T827600
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Law and Justice |
E17889
|
entity |
| Predicate | hasHeldOffice |
P1827
|
FINISHED |
| Object | ruling party of Poland |
—
|
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: ruling party of Poland | Statement: [Law and Justice, hasHeldOffice, ruling party of Poland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHeldOffice Context triple: [Law and Justice, hasHeldOffice, ruling party of Poland]
-
A.
succeededInOffice
Indicates that one officeholder directly followed another in holding the same official position.
-
B.
heldJudicialPositionIn
Indicates that an entity served in an official judicial role or office within a specified jurisdiction or court.
-
C.
officePreviouslyHeldBy
Indicates that a particular office or position was formerly occupied by a specified person or entity.
-
D.
memberHoldsOffice
Indicates that a member occupies or serves in a specific official position or office within an organization or governing body.
-
E.
servedAs
chosen
Indicates that one entity held and performed the role, position, or function associated with another entity for some period of time.
- 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_69a4937c9c188190aaa216f6b466f452 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4ab99b1e48190afad1f073348b29a |
completed | March 1, 2026, 9:11 p.m. |
| PD | Predicate disambiguation | batch_69a4aa79a6488190a634388e071ed9b7 |
completed | March 1, 2026, 9:07 p.m. |
Created at: March 1, 2026, 7:38 p.m.