Triple
T12744007
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aubenas |
E304556
|
entity |
| Predicate | departmentCapitalRole |
P18085
|
FINISHED |
| Object | economic hub of southern Ardèche |
—
|
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: economic hub of southern Ardèche | Statement: [Aubenas, departmentCapitalRole, economic hub of southern Ardèche]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: departmentCapitalRole Context triple: [Aubenas, departmentCapitalRole, economic hub of southern Ardèche]
-
A.
capitalRoleUntil
Indicates that an entity served in the role of capital of another entity up to (but not necessarily including) a specified end time.
-
B.
hasCapitalRole
chosen
Indicates that an entity holds an official role, function, or status specifically associated with a capital city.
-
C.
headquartersRole
Indicates that an entity serves in an official capacity or role at the headquarters of an organization.
-
D.
portfolioRole
Indicates the specific function, capacity, or position an entity holds within a portfolio or collection of assets.
-
E.
hasHeadquartersRoleFor
Indicates that an entity holds a specific role or position within the headquarters of another entity.
- 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_69d7bdf1426c8190a4402e1c4cdec33a |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96d89ea70819098c470344f172167 |
completed | April 10, 2026, 9:37 p.m. |
| PD | Predicate disambiguation | batch_69d96406e97c8190b79081039847115c |
completed | April 10, 2026, 8:56 p.m. |
Created at: April 9, 2026, 5:26 p.m.