Triple
T12103380
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sadd el-Ali |
E288242
|
entity |
| Predicate | designedToControl |
P49579
|
FINISHED |
| Object | annual Nile floods |
—
|
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: annual Nile floods | Statement: [Sadd el-Ali, designedToControl, annual Nile floods]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designedToControl Context triple: [Sadd el-Ali, designedToControl, annual Nile floods]
-
A.
usedToControl
chosen
Indicates that one entity employed another as a means or tool to exercise control or regulation over something.
-
B.
canBeControlledFrom
Indicates that one entity has the ability or authority to operate, direct, or manage another entity remotely or indirectly.
-
C.
aimsToControl
Indicates an intention or effort by one entity to gain power over, direct, or regulate another entity or situation.
-
D.
utilitiesControlledBy
Indicates that one entity has authority over, management of, or operational control of another entity’s utilities or utility services.
-
E.
exportControl
Indicates that an entity is subject to rules or restrictions governing the transfer or export of goods, services, or information across borders.
- 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_69d6ab4a5c448190a110d1273314b21a |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d9164ada5081908676bd9e5947268a |
completed | April 10, 2026, 3:24 p.m. |
| PD | Predicate disambiguation | batch_69d9150497408190921334d21503375a |
completed | April 10, 2026, 3:19 p.m. |
Created at: April 8, 2026, 9:48 p.m.