Triple
T36264062
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Economy of Leicester |
E892172
|
entity |
| Predicate | transitioningTowards |
P36477
|
FINISHED |
| Object | knowledge-based industries |
—
|
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: knowledge-based industries | Statement: [Economy of Leicester, transitioningTowards, knowledge-based industries]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transitioningTowards Context triple: [Economy of Leicester, transitioningTowards, knowledge-based industries]
-
A.
transition
Indicates a change of state or condition from one form, phase, or situation to another.
-
B.
transitionTo
chosen
Indicates a change in state, condition, or phase from one defined status to another.
-
C.
continuesToward
Indicates that an entity maintains its movement or progression in the direction of a specified target or destination.
-
D.
transitionTopic
Indicates a shift in focus from one topic to another within a discourse or interaction.
-
E.
transiting
Indicates that an entity is in the process of passing through, across, or between locations or states, typically as part of a journey or transfer.
- 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_69f76e4699188190af045b11a840ce31 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69ff7c96e6dc8190b89554480ebcea39 |
completed | May 9, 2026, 6:27 p.m. |
| PD | Predicate disambiguation | batch_69ff7c2381748190ad9a2176e0e478cd |
completed | May 9, 2026, 6:25 p.m. |
Created at: May 3, 2026, 4:09 p.m.