Triple
T23848116
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Unilateral Declaration of Egyptian Independence (1922) |
E592079
|
entity |
| Predicate | reservedArea |
P4923
|
FINISHED |
| Object | defense of 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: defense of Egypt | Statement: [Unilateral Declaration of Egyptian Independence (1922), reservedArea, defense of Egypt]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reservedArea Context triple: [Unilateral Declaration of Egyptian Independence (1922), reservedArea, defense of Egypt]
-
A.
regulatedArea
Indicates that an area is subject to specific rules, controls, or restrictions imposed by an authority.
-
B.
reservePositionArea
Indicates that an area is designated or set aside to hold or reserve a specific position or set of positions.
-
C.
reservedFor
chosen
Indicates that something is set aside or allocated specifically for the use, benefit, or purpose of a particular entity or group.
-
D.
representedArea
Indicates that one entity serves as a representation or depiction of a particular area or region.
-
E.
occupiedRegion
Indicates that an entity has taken control of and is currently holding a specific geographic area or region.
- 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_69e25d221d908190b9b502ad31e66a3f |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1c9851f988190af39f57f9b71da03 |
completed | April 29, 2026, 9:04 a.m. |
| PD | Predicate disambiguation | batch_69f1614612b481908c45d99e588882f9 |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 8:10 p.m.