Triple
T32199807
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | World War I in Persia |
E822500
|
entity |
| Predicate | hasLegalStatusOfPersia |
P2250
|
FINISHED |
| Object | neutral |
—
|
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: neutral | Statement: [World War I in Persia, hasLegalStatusOfPersia, neutral]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLegalStatusOfPersia Context triple: [World War I in Persia, hasLegalStatusOfPersia, neutral]
-
A.
legalStatusUnderPahlavi
Indicates the legal status or condition an entity held under the laws and governance of the Pahlavi regime in Iran.
-
B.
hasLegalStatusInSaudiLaw
Indicates that an entity possesses a specific legal status or recognition under the laws and regulations of Saudi Arabia.
-
C.
statusInIran
Indicates the legal, social, or political standing or condition of an entity specifically within the context of Iran.
-
D.
hasLegalStatus
chosen
Indicates that an entity possesses a particular legal classification, recognition, or standing under law.
-
E.
hasLegalStatusInSudan
Indicates that an entity holds a recognized legal status or standing within the jurisdiction of Sudan.
- 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_69f349093174819086e633c190a51aa8 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fd5f29b1988190877764ef2a399c7f |
completed | May 8, 2026, 3:57 a.m. |
| PD | Predicate disambiguation | batch_69fd5e30194c819085b5ce586122ab37 |
completed | May 8, 2026, 3:53 a.m. |
Created at: May 1, 2026, 12:36 a.m.