Triple
T29034854
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jabrayil |
E737829
|
entity |
| Predicate | postWarProcess |
P12962
|
FINISHED |
| Object | reconstruction |
—
|
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: reconstruction | Statement: [Jabrayil, postWarProcess, reconstruction]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: postWarProcess Context triple: [Jabrayil, postWarProcess, reconstruction]
-
A.
postWarFunction
Indicates how something operated, was used, or what role it served in the period following a war.
-
B.
postwarOutcome
chosen
Indicates the result or consequences that follow for a party or situation after a war has ended.
-
C.
postWarOrder
Indicates the arrangement of political, economic, and social relations established among actors after a war has ended.
-
D.
postWarOccupation
Indicates that one entity occupied, administered, or controlled another entity or territory in the period following a war.
-
E.
postWarHistory
Indicates a relationship where something concerns, describes, or belongs to the historical period and events following a specific war.
- 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_69f077efb3848190b41574e1670f6ae2 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f6603be0cc8190ba34acec15092a98 |
completed | May 2, 2026, 8:36 p.m. |
| PD | Predicate disambiguation | batch_69f65c2376a08190be5215171e908e69 |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 28, 2026, 9:57 a.m.