Triple
T20322381
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eastern Ghouta |
E492235
|
entity |
| Predicate | preWarCharacterizedBy |
P79060
|
FINISHED |
| Object | intensive agriculture |
—
|
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: intensive agriculture | Statement: [Eastern Ghouta, preWarCharacterizedBy, intensive agriculture]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: preWarCharacterizedBy Context triple: [Eastern Ghouta, preWarCharacterizedBy, intensive agriculture]
-
A.
preWarCharacter
Indicates that a character existed or had a particular state or role prior to a specified war or conflict.
-
B.
preWarRole
Indicates the role, position, or function an entity held before the onset of a specified war or conflict.
-
C.
preWarContinuityWith
Indicates that a relationship, structure, or condition remains consistent with or directly continues from its state before a war or major conflict.
-
D.
preWarCountry
Indicates that a country existed or held a particular status prior to a specified war or major armed conflict.
-
E.
prewarStatus
chosen
Indicates the condition, role, or circumstances of an entity as they existed before a specific war or armed conflict.
- 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_69e0b4a0134081909113563e1c3ba68a |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6778c4430819083b17da5067b88ef |
completed | April 20, 2026, 6:59 p.m. |
| PD | Predicate disambiguation | batch_69e5762655ac8190a8cc48a29fa2c0c4 |
completed | April 20, 2026, 12:41 a.m. |
Created at: April 16, 2026, 11:20 a.m.