Triple
T18573336
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Béarnaise culture |
E453924
|
entity |
| Predicate | regionalMovement |
P132644
|
FINISHED |
| Object | Béarnais cultural revival |
—
|
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: Béarnais cultural revival | Statement: [Béarnaise culture, regionalMovement, Béarnais cultural revival]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regionalMovement Context triple: [Béarnaise culture, regionalMovement, Béarnais cultural revival]
-
A.
regionalType
Indicates the classification of a region according to its designated type or category within a broader geographic or administrative system.
-
B.
region1
Indicates that one entity is the first or primary region associated with, containing, or encompassing another entity.
-
C.
countryRegionalOrganization
Indicates that a country is a member of, or affiliated with, a specific regional organization.
-
D.
regionalOrientation
Indicates how something is directed, aligned, or focused toward a particular geographic region or area.
-
E.
developmentRegion
Indicates the geographic or administrative region in which something is developed, produced, or primarily created.
- F. None of above. chosen
Provenance (4 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_69d8d38974308190a9174430ef256b73 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e543c7f63c81909b5d5764ffd20234 |
completed | April 19, 2026, 9:06 p.m. |
| PD | Predicate disambiguation | batch_69e478c98d4c81909d37a0e72c6e7bd0 |
completed | April 19, 2026, 6:40 a.m. |
| PDg | Predicate description generation | batch_69e484121cd48190bf583b4c94636a30 |
completed | April 19, 2026, 7:28 a.m. |
Created at: April 10, 2026, 11:43 a.m.