Triple
T37347859
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sainte-Florine |
E927230
|
entity |
| Predicate | isLocatedInCulturalRegion |
P1968
|
FINISHED |
| Object | Auvergne |
—
|
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: Auvergne | Statement: [Sainte-Florine, isLocatedInCulturalRegion, Auvergne]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isLocatedInCulturalRegion Context triple: [Sainte-Florine, isLocatedInCulturalRegion, Auvergne]
-
A.
isCulturalAreaFor
Indicates that one entity serves as a designated cultural area or space intended for the cultural activities, practices, or identity of another entity.
-
B.
culturalRegion
chosen
Indicates that an entity is located in, associated with, or belongs to a specific cultural region or cultural area.
-
C.
namedForCulturalRegion
Indicates that something is given a name derived from or honoring a specific cultural region.
-
D.
isCulturalArea
Indicates that a given area is recognized or designated as a cultural region, characterized by shared cultural traits, practices, or heritage.
-
E.
culturalAreaIncludes
Indicates that a broader cultural area encompasses or contains a smaller cultural region or entity within its scope.
- 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_69f76eb5e034819088e53ab5b7909a68 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fd2cf39b0c8190811b8a6fa9410560 |
completed | May 8, 2026, 12:23 a.m. |
| PD | Predicate disambiguation | batch_69fd2ad8dd988190a9899701ba00d917 |
completed | May 8, 2026, 12:14 a.m. |
Created at: May 3, 2026, 4:16 p.m.