Triple
T23010305
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Morini |
E572886
|
entity |
| Predicate | regionCenterNear |
P84435
|
FINISHED |
| Object | modern Boulogne-sur-Mer |
—
|
LITERAL 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: modern Boulogne-sur-Mer | Statement: [Morini, regionCenterNear, modern Boulogne-sur-Mer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regionCenterNear Context triple: [Morini, regionCenterNear, modern Boulogne-sur-Mer]
-
A.
hasRegionalCenterNearby
chosen
Indicates that a regional center is located in close proximity to the referenced entity.
-
B.
administrativeCentreNearby
Indicates that an administrative centre is located close to the referenced entity in geographic or spatial terms.
-
C.
nearestTownCenter
Indicates that one location is the closest town center to another specified point or area.
-
D.
nearestMajorCenter
Indicates that one location is the closest significant urban or population center relative to another location.
-
E.
hasRegionCenter
Indicates that a region is associated with a specific central point or location that serves as its geometric or administrative center.
- 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_69e245b764cc8190a51be76f1d9611e1 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f18359f5548190b15a139eb09e30a0 |
completed | April 29, 2026, 4:04 a.m. |
| PD | Predicate disambiguation | batch_69ef3b9cd5488190bcd23183179f48cd |
completed | April 27, 2026, 10:34 a.m. |
Created at: April 17, 2026, 3:51 p.m.