Triple
T28793780
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Confluentes |
E727029
|
entity |
| Predicate | coordinateWithModernCity |
P132960
|
FINISHED |
| Object | Koblenz 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: Koblenz city center | Statement: [Confluentes, coordinateWithModernCity, Koblenz city center]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coordinateWithModernCity Context triple: [Confluentes, coordinateWithModernCity, Koblenz city center]
-
A.
modernLocationOfCity
Indicates that a historical or former city is located within the boundaries of a specified modern administrative or geographic entity.
-
B.
containsModernCity
Indicates that one geographic or administrative region includes within its boundaries a currently existing modern city.
-
C.
refersToModernCity
Indicates that one entity is a reference to, or designation for, a contemporary city in the modern world.
-
D.
hasModernNearbyCity
chosen
Indicates that an entity is located near or in proximity to a contemporary, currently existing city.
-
E.
centerCityModernName
Indicates that the object is the current or modern name of the city that serves as the center or capital associated with the subject.
- 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_69f0319b7c44819085736bcc256185e6 |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f69383222c81909d8baa04129d5c81 |
completed | May 3, 2026, 12:14 a.m. |
| PD | Predicate disambiguation | batch_69f690eb1e948190aab41a89969519a5 |
completed | May 3, 2026, 12:03 a.m. |
Created at: April 28, 2026, 6:24 a.m.