Triple
T25077858
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Montfort |
E628100
|
entity |
| Predicate | typicalCulturalSphere |
P14191
|
FINISHED |
| Object | Francophone world |
—
|
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: Francophone world | Statement: [Montfort, typicalCulturalSphere, Francophone world]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalCulturalSphere Context triple: [Montfort, typicalCulturalSphere, Francophone world]
-
A.
culturalRegion
Indicates that an entity is located in, associated with, or belongs to a specific cultural region or cultural area.
-
B.
culturalSphere
chosen
Indicates that one entity belongs to, is influenced by, or participates in the cultural domain, tradition, or milieu defined by another entity.
-
C.
continentOfCulturalContext
Indicates that a cultural context is associated with, originates from, or is primarily situated within a specific continent.
-
D.
namedForCulturalRegion
Indicates that something is given a name derived from or honoring a specific cultural region.
-
E.
culturalType
Indicates the classification of something according to its cultural category, style, or tradition.
- 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_69e2ff2e73f881909992bf3eda5c25cb |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f7817daf00819098936402e75ab0a6 |
completed | May 3, 2026, 5:10 p.m. |
| PD | Predicate disambiguation | batch_69f780fc5ed88190b7200ee5a29940af |
completed | May 3, 2026, 5:08 p.m. |
Created at: April 18, 2026, 6:21 a.m.