Triple
T27975769
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sepahan SC |
E706484
|
entity |
| Predicate | isFromCityWithHistoricArchitecture |
P163996
|
FINISHED |
| Object | Isfahan |
—
|
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: Isfahan | Statement: [Sepahan SC, isFromCityWithHistoricArchitecture, Isfahan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isFromCityWithHistoricArchitecture Context triple: [Sepahan SC, isFromCityWithHistoricArchitecture, Isfahan]
-
A.
isHistoricalCity
Indicates that a city has historical significance, typically due to its age, past events, or preserved heritage.
-
B.
passesHistoricCity
Indicates that a route, path, or entity travels through or goes by a city recognized for its historical significance.
-
C.
hasHistoricCenterNearby
Indicates that one entity is located close to another entity that serves as a historic center or historically significant core area.
-
D.
hasHistoricCity
Indicates that an entity possesses, contains, or is associated with a city recognized for its historical significance.
-
E.
isInHistoricCenterOf
Indicates that one entity is located within the historic center area of another entity (typically a city or town).
- 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_69ef96b7f330819090f315318ba6977e |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f6416fbf4081909b0913c337927fc4 |
completed | May 2, 2026, 6:24 p.m. |
| PD | Predicate disambiguation | batch_69f63c6a8474819091b8c6fe98e3862d |
completed | May 2, 2026, 6:03 p.m. |
| PDg | Predicate description generation | batch_69f63fd4f7448190930c723ba7cfce62 |
completed | May 2, 2026, 6:17 p.m. |
Created at: April 27, 2026, 7:41 p.m.