Triple
T23649943
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | conventus of Rotomagus |
E584139
|
entity |
| Predicate | centeredInModernCity |
P58091
|
FINISHED |
| Object | Rouen |
—
|
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: Rouen | Statement: [conventus of Rotomagus, centeredInModernCity, Rouen]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: centeredInModernCity Context triple: [conventus of Rotomagus, centeredInModernCity, Rouen]
-
A.
containsModernCity
chosen
Indicates that one geographic or administrative region includes within its boundaries a currently existing modern city.
-
B.
modernCityIs
Indicates that something possesses the characteristics or status of being a modern city.
-
C.
hasModernNearbyCity
Indicates that an entity is located near or in proximity to a contemporary, currently existing city.
-
D.
isModernistCity
Indicates that a city embodies characteristics of modernist urban design, architecture, and planning principles.
-
E.
modernCityBuiltAround
Indicates that a contemporary or recently developed city has been constructed encircling or surrounding a particular central feature, structure, or area.
- 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_69e248fefafc81909656921192f30e80 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b2885b408190a43dfed93309a4d6 |
completed | April 29, 2026, 7:26 a.m. |
| PD | Predicate disambiguation | batch_69f118d7903c8190bb590a71771e93af |
completed | April 28, 2026, 8:30 p.m. |
Created at: April 17, 2026, 6:49 p.m.