Triple
T29274316
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U.S. Embassy in Jerusalem |
E742207
|
entity |
| Predicate | recognizedCapital |
P75183
|
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: [U.S. Embassy in Jerusalem, recognizedCapital, Jerusalem]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recognizedCapital Context triple: [U.S. Embassy in Jerusalem, recognizedCapital, Jerusalem]
-
A.
capitalRenamedFrom
Indicates that a capital city previously had a different name, specifying the former name from which it was renamed.
-
B.
capitalRenamedTo
Indicates that a place’s status or name as a capital city has been changed to a new capital designation or name.
-
C.
capitalSince
Indicates that an entity has served as the capital of another entity starting from a specified point in time.
-
D.
capitalRepresentation
chosen
Indicates that one entity serves as the capital city or capital seat representing another entity, such as a country, state, or region.
-
E.
possibleCapital
Indicates that a location is a candidate or potential capital city of a given political or administrative entity.
- 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_69f0912124d48190a046642b69407f4c |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69f7431c0eec81909ead443e07d75e18 |
completed | May 3, 2026, 12:44 p.m. |
| PD | Predicate disambiguation | batch_69f74143cf708190a12d487884298437 |
completed | May 3, 2026, 12:36 p.m. |
Created at: April 28, 2026, 12:50 p.m.