Triple
T24887566
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Al-ʿĀṣī |
E622899
|
entity |
| Predicate | hasHistoricalCityOnBank |
P7935
|
FINISHED |
| Object | Antioch |
—
|
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: Antioch | Statement: [Al-ʿĀṣī, hasHistoricalCityOnBank, Antioch]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHistoricalCityOnBank Context triple: [Al-ʿĀṣī, hasHistoricalCityOnBank, Antioch]
-
A.
hasCityOnBank
chosen
Indicates that a city is located on the bank of a particular river or body of water.
-
B.
hasHistoricCity
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.
capitalOrMajorCityHistorically
Indicates that a place has historically served as a capital or as a major, centrally important city for a political or cultural entity.
-
E.
hasAncientCityState
Indicates that one entity possesses, contains, or is associated with an ancient city-state as part of its historical or geographical context.
- 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_69e2fac4aa848190b3446a3922cec150 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f6135293908190809e255bf6334760 |
completed | May 2, 2026, 3:08 p.m. |
| PD | Predicate disambiguation | batch_69f611a72780819082f44e66ca2c6ac9 |
completed | May 2, 2026, 3 p.m. |
Created at: April 18, 2026, 5:25 a.m.