Triple
T4571748
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Auxerre |
E123045
|
entity |
| Predicate | regionallyImportantAs |
P12510
|
FINISHED |
| Object | cultural center |
—
|
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: cultural center | Statement: [Auxerre, regionallyImportantAs, cultural center]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regionallyImportantAs Context triple: [Auxerre, regionallyImportantAs, cultural center]
-
A.
hasRegionalSignificance
chosen
Indicates that something holds particular importance, influence, or relevance within a specific geographic region.
-
B.
notableRegionOfSettlement
Indicates that a specified region is a significant or prominent place where an entity is or has been settled.
-
C.
notableInRegion
Indicates that an entity is recognized as notable, prominent, or significant within a specified geographic region.
-
D.
regionallyAssociatedWith
Indicates that two entities are connected or related based on sharing the same or overlapping geographic or regional context.
-
E.
regionallyRecognizedAs
Indicates that an entity is acknowledged or designated under a specific name, status, or classification within a particular geographic region or locality.
- 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_69bd46466c7081909d07f36be2d08804 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd58c5afa48190bb8505e2cc16e89f |
completed | March 20, 2026, 2:25 p.m. |
| PD | Predicate disambiguation | batch_69bd5227063c8190973155a875b013a7 |
completed | March 20, 2026, 1:56 p.m. |
Created at: March 20, 2026, 1:10 p.m.