Triple
T24322947
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Palestinian Declaration of Independence |
E613018
|
entity |
| Predicate | declaresCapital |
P155554
|
FINISHED |
| Object | Jerusalem |
—
|
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: Jerusalem | Statement: [Palestinian Declaration of Independence, declaresCapital, Jerusalem]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: declaresCapital Context triple: [Palestinian Declaration of Independence, declaresCapital, Jerusalem]
-
A.
deJureCapitalOf
Indicates that one place is the legally designated (official) capital of a political entity, regardless of where its actual governing institutions are located.
-
B.
basedInCapital
Indicates that an entity is located or has its main base of operations in a capital city.
-
C.
coCapitalOf
Indicates that two or more cities share the status of being capital cities of the same political or administrative entity.
-
D.
regionCapital
Indicates that one entity is the capital city or administrative center of a specified region.
-
E.
departmentCapitalOf
Indicates that a location serves as the administrative capital of a specified department (an administrative division).
- 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_69e2d7db6d5c819091194918157a7c1f |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f292ad4cc881908794b501cf70b7a1 |
completed | April 29, 2026, 11:22 p.m. |
| PD | Predicate disambiguation | batch_69f1c45f45888190a9ccc225906c34bd |
completed | April 29, 2026, 8:42 a.m. |
| PDg | Predicate description generation | batch_69f1c6d4e99081909f61899eccafb73e |
completed | April 29, 2026, 8:52 a.m. |
Created at: April 18, 2026, 1:52 a.m.