Triple
T199377
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arab League |
E4067
|
entity |
| Predicate | readmissionOfSyria |
P8023
|
FINISHED |
| Object | 2023 |
—
|
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: 2023 | Statement: [Arab League, readmissionOfSyria, 2023]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: readmissionOfSyria Context triple: [Arab League, readmissionOfSyria, 2023]
-
A.
countrySurrendering
Indicates that one country formally yields to another country’s authority or control, typically ending a conflict or war.
-
B.
militaryConflict
Indicates a relationship where two or more parties are engaged in organized, armed hostilities or warfare against each other.
-
C.
UNResolution
Indicates that there exists a formal decision or declaration adopted by the United Nations, typically expressing a collective position, directive, or recommendation regarding an issue.
-
D.
reform
Indicates bringing about significant changes to an existing system, practice, or entity in order to improve or correct it.
-
E.
UNRecognition
Indicates that an entity is formally acknowledged or recognized by the United Nations as having a particular status, role, or legitimacy.
- F. None of above. chosen
Provenance (4 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_69a254bca59881909a15e1496f1508c7 |
completed | Feb. 28, 2026, 2:36 a.m. |
| NER | Named-entity recognition | batch_69a25bcc6dc88190b8c24b485588dfe4 |
completed | Feb. 28, 2026, 3:06 a.m. |
| PD | Predicate disambiguation | batch_69a25b4886b48190b46fd2244648a098 |
completed | Feb. 28, 2026, 3:04 a.m. |
| PDg | Predicate description generation | batch_69a25bc6ba208190aa8bec59d32f95fd |
completed | Feb. 28, 2026, 3:06 a.m. |
Created at: Feb. 28, 2026, 2:44 a.m.