Triple
T28513800
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GERD |
E721560
|
entity |
| Predicate | disputeParty |
P83991
|
FINISHED |
| Object | Egypt |
—
|
NE NERFINISHED |
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: Egypt | Statement: [GERD, disputeParty, Egypt]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: disputeParty Context triple: [GERD, disputeParty, Egypt]
-
A.
hasDisputeParties
chosen
Indicates that a dispute involves the specified parties as participants in the conflict or disagreement.
-
B.
negotiatingParty
Indicates that an entity is actively involved as a participant in a negotiation process with another entity.
-
C.
decliningParty
Indicates that an entity refuses, rejects, or turns down an offer, request, or proposal made by another entity.
-
D.
disputeResolvedBy
Indicates that a particular dispute or conflict has been settled or resolved through the actions, decision, or intervention of a specified party or process.
-
E.
disputeInvolves
Indicates that a particular dispute includes or concerns the specified entities as participants or parties to the 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_69f01a5c072081908c7b04bcf6478da9 |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f64f77c86c8190bb05cffae7c17a00 |
completed | May 2, 2026, 7:24 p.m. |
| PD | Predicate disambiguation | batch_69f64cb0d8008190912e1430cfaf92aa |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 28, 2026, 3:15 a.m.