Triple
T33466134
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Abu Ishaq Inju |
E857047
|
entity |
| Predicate | notableCityInRealm |
P41762
|
FINISHED |
| Object | Isfahan |
E68692
|
NE 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: Isfahan | Statement: [Abu Ishaq Inju, notableCityInRealm, Isfahan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableCityInRealm Context triple: [Abu Ishaq Inju, notableCityInRealm, Isfahan]
-
A.
notableCityIncluded
chosen
Indicates that a notable or significant city is contained within, or is part of, a larger geographic or administrative entity.
-
B.
notableHumanSettlement
Indicates that a location is recognized as a significant or noteworthy human settlement, such as a city, town, or village.
-
C.
notableCityOfOperation
Indicates that a city is a primary or particularly significant location where an entity conducts its operations or activities.
-
D.
notableTerminusCity
Indicates that a city is notably recognized as a terminus (endpoint) of a route, line, or network.
-
E.
notableInCity
Indicates that an entity is particularly prominent, recognized, or significant within a specific city.
- F. None of above.
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_69f34973461481909c701c98ebd75623 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a39c3d55c908190a59ddb6d80a4f8fa |
completed | June 22, 2026, 11:23 p.m. |
| PD | Predicate disambiguation | batch_6a0379f505c88190ac0879ab422c3054 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:37 a.m.