Triple
T312452
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nubians |
E7635
|
entity |
| Predicate | consequenceOfEvent |
P812
|
FINISHED |
| Object | large-scale displacement in Egypt |
—
|
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: large-scale displacement in Egypt | Statement: [Nubians, consequenceOfEvent, large-scale displacement in Egypt]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: consequenceOfEvent Context triple: [Nubians, consequenceOfEvent, large-scale displacement in Egypt]
-
A.
hasConsequence
chosen
Indicates that one event, action, or condition leads to or results in another as its outcome or effect.
-
B.
causeOf
Indicates that one entity brings about, produces, or is responsible for the occurrence or existence of another entity or event.
-
C.
after
Indicates that one event, state, or action occurs later in time than another, following it in temporal order.
-
D.
conquestEvent
Indicates an event in which one party gains control over another entity or territory through force or domination.
-
E.
subsequentConflict
Indicates that one conflict occurs after and is temporally subsequent to another 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_69a2e7e7af7881908890039d6be4e9b8 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ea4aa16881909b2c8404b85992df |
completed | Feb. 28, 2026, 1:14 p.m. |
| PD | Predicate disambiguation | batch_69a2e940b9e8819092b821ff17ed026b |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:07 p.m.