Triple
T34506396
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zambian Jews |
E885898
|
entity |
| Predicate | mainCitiesHistorically |
P3786
|
FINISHED |
| Object | Livingstone |
—
|
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: Livingstone | Statement: [Zambian Jews, mainCitiesHistorically, Livingstone]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainCitiesHistorically Context triple: [Zambian Jews, mainCitiesHistorically, Livingstone]
-
A.
capitalOrMajorCityHistorically
Indicates that a place has historically served as a capital or as a major, centrally important city for a political or cultural entity.
-
B.
hasHistoricCity
chosen
Indicates that an entity possesses, contains, or is associated with a city recognized for its historical significance.
-
C.
isHistoricalCity
Indicates that a city has historical significance, typically due to its age, past events, or preserved heritage.
-
D.
historicalCityCorrespondence
Indicates a relationship where one city historically corresponds to, or is considered the historical counterpart or predecessor of, another city.
-
E.
focusCityHistory
Indicates that there is a historical or context-defining relationship between a focal city and its past events, developments, or status.
- 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_69f349cc0220819081f154c6964f4dc2 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fd19f791f48190bbb6f6047f9ddc59 |
completed | May 7, 2026, 11:02 p.m. |
| PD | Predicate disambiguation | batch_69fd0df365948190bc9bfc7ffd46acd8 |
completed | May 7, 2026, 10:10 p.m. |
Created at: May 1, 2026, 2:01 a.m.