Triple
T12011886
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | عكّا |
E285922
|
entity |
| Predicate | مدينة_تاريخية |
P32937
|
FINISHED |
| Object | نعم |
—
|
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: نعم | Statement: [عكّا, مدينة_تاريخية, نعم]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: مدينة_تاريخية Context triple: [عكّا, مدينة_تاريخية, نعم]
-
A.
passesHistoricCity
Indicates that a route, path, or entity travels through or goes by a city recognized for its historical significance.
-
B.
focusCityHistory
Indicates that there is a historical or context-defining relationship between a focal city and its past events, developments, or status.
-
C.
ancientCity
chosen
Indicates that the subject is a historically old or long-established city, typically originating from ancient times.
-
D.
capitalHistoric
Indicates that a location has served as a capital city at some point in history, even if it is not the current capital.
-
E.
isHistoricCenterOf
Indicates that a place serves as the historically significant core or original central area of another location, typically a city or town.
- 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_69d6ab45a368819084fce08bf0dc3705 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d903d7777481908cd5a001f75e2ee3 |
completed | April 10, 2026, 2:06 p.m. |
| PD | Predicate disambiguation | batch_69d902b245cc8190af96a9c2bd9c6250 |
completed | April 10, 2026, 2:01 p.m. |
Created at: April 8, 2026, 9:46 p.m.