Triple
T23649973
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | conventus of Cenabum |
E584140
|
entity |
| Predicate | modernCenterLocatedAt |
P8489
|
FINISHED |
| Object | Orléans |
—
|
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: Orléans | Statement: [conventus of Cenabum, modernCenterLocatedAt, Orléans]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: modernCenterLocatedAt Context triple: [conventus of Cenabum, modernCenterLocatedAt, Orléans]
-
A.
centralLocation
Indicates that one entity serves as the primary or central place associated with another entity.
-
B.
municipalCentre
Indicates that a location functions as the primary administrative or civic center for a municipality.
-
C.
modernLocality
chosen
Indicates that an entity is located in, associated with, or corresponds to a present-day geographic or administrative locality.
-
D.
urbanCenterDevelopedBy
Indicates that an urban center was created, planned, or significantly developed through the actions or initiatives of a particular agent (such as an organization, authority, or project).
-
E.
hasCityCentreLocation
Indicates that something is located in, or directly associated with, the central area of a city.
- 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.