Triple
T20709457
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sambre valley region |
E508993
|
entity |
| Predicate | currentDevelopmentFocus |
P129848
|
FINISHED |
| Object | economic reconversion |
—
|
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 reconversion | Statement: [Sambre valley region, currentDevelopmentFocus, economic reconversion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: currentDevelopmentFocus Context triple: [Sambre valley region, currentDevelopmentFocus, economic reconversion]
-
A.
hasDevelopmentFocus
chosen
Indicates that an entity is primarily concerned with or directed toward a particular area, goal, or aspect of development.
-
B.
developmentFor
Indicates that one entity is created, adapted, or advanced specifically for the benefit, use, or purpose of another entity.
-
C.
developmentDirection
Indicates the primary orientation or path along which something grows, progresses, or evolves over time.
-
D.
mainDevelopmentPeriod
Indicates the primary time span during which the main development or formation of something took place.
-
E.
deploymentFocus
Indicates the primary area, target, or aspect that a deployment is directed toward or concentrated on.
- 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_69e0b4c40ad88190b81f77695366d328 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c1961090819090daf7254f90a176 |
completed | April 21, 2026, 12:15 a.m. |
| PD | Predicate disambiguation | batch_69e5c044d1108190b2b5d25de23f6401 |
completed | April 20, 2026, 5:57 a.m. |
Created at: April 16, 2026, 12:14 p.m.