Triple
T34976028
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Krakozhian |
E1008678
|
entity |
| Predicate | passportValidityInPlot |
P43256
|
FINISHED |
| Object | suspended due to political unrest |
—
|
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: suspended due to political unrest | Statement: [Krakozhian, passportValidityInPlot, suspended due to political unrest]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: passportValidityInPlot Context triple: [Krakozhian, passportValidityInPlot, suspended due to political unrest]
-
A.
borderPass
Indicates that one entity crosses or moves through the boundary separating two regions or jurisdictions.
-
B.
visaPolicyInstrument
Indicates that a particular policy, rule, or legal instrument is used to define, regulate, or implement a visa policy between entities.
-
C.
ticketValidityCovers
Indicates that the validity period or scope of a ticket extends to and includes a specified time, location, service, or condition.
-
D.
canHoldPassport
Indicates that an entity is legally eligible or permitted to possess a passport.
-
E.
passportRevokedBy
chosen
Indicates that an authority or entity has officially canceled or withdrawn the validity of a person's passport.
- 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_69f76dc78a308190a1ac29ad4a9a4895 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78710282c81909146dc0be91e983f |
completed | May 3, 2026, 5:34 p.m. |
| PD | Predicate disambiguation | batch_69f784162134819098413482ef52042f |
completed | May 3, 2026, 5:21 p.m. |
Created at: May 3, 2026, 4:01 p.m.