Triple
T20345079
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gladbeck |
E495844
|
entity |
| Predicate | hasTransitionedTo |
P6197
|
FINISHED |
| Object | diversified economy |
—
|
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: diversified economy | Statement: [Gladbeck, hasTransitionedTo, diversified economy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTransitionedTo Context triple: [Gladbeck, hasTransitionedTo, diversified economy]
-
A.
laterTransitionedTo
Indicates that an entity changed or evolved into another state, role, or condition at a subsequent point in time.
-
B.
hasTransitionType
Indicates the type or category of transition that occurs between two states, phases, or conditions.
-
C.
transitionedThrough
Indicates that an entity passed from one state, phase, or condition to another by way of an intermediate state, phase, or condition.
-
D.
transitionedInto
chosen
Indicates that one entity changed state, form, role, or condition to become another specified state or entity.
-
E.
hasTransitionUpperLevel
Indicates a relationship where something possesses or is associated with an upper-level transition state or phase within a hierarchical or multi-level process.
- 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_69e0b4a3320881909495ae8bc30bc2dc |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e67838744481909069b76b25dd4bb9 |
completed | April 20, 2026, 7:02 p.m. |
| PD | Predicate disambiguation | batch_69e57636b4808190bc2855af48a3ccdc |
completed | April 20, 2026, 12:41 a.m. |
Created at: April 16, 2026, 11:24 a.m.