Triple
T18119066
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kanīsat al-Qiddīs Jirjis |
E433684
|
entity |
| Predicate | near |
P350
|
FINISHED |
| Object | Lod city center |
—
|
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: Lod city center | Statement: [Kanīsat al-Qiddīs Jirjis, near, Lod city center]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Lod city center Context triple: [Kanīsat al-Qiddīs Jirjis, near, Lod city center]
-
A.
Lod city center
chosen
Lod city center is the main commercial and civic hub of the city of Lod in central Israel, featuring shops, services, and historic sites.
-
B.
Lod
Lod is a historic city in central Israel, near Tel Aviv, known for its ancient past and for hosting Ben Gurion International Airport.
-
C.
Centrum
Centrum is the central urban district and main commercial area of the Dutch city of Meppel.
-
D.
Centrum
Centrum is the central district and main urban core of the Dutch municipality of Ridderkerk.
-
E.
Centrum
Centrum is the historic city center district of Amsterdam, known for its canals, landmarks, and bustling markets.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8b909e8cc81908df4cc2b8ea6d11f |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4ddd843e88190abbc173dbc9b450a |
completed | April 19, 2026, 1:51 p.m. |
Created at: April 10, 2026, 10:28 a.m.