Triple
T9380796
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Finnieston Crane |
E225775
|
entity |
| Predicate | industrialEra |
P34306
|
FINISHED |
| Object | 20th century heavy engineering |
—
|
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: 20th century heavy engineering | Statement: [Finnieston Crane, industrialEra, 20th century heavy engineering]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: industrialEra Context triple: [Finnieston Crane, industrialEra, 20th century heavy engineering]
-
A.
modernIndustry
Indicates that an entity operates within or is characteristic of contemporary, technologically advanced industrial practices and sectors.
-
B.
timePeriodOfIndustrialization
chosen
Indicates the time period during which a given entity underwent industrialization.
-
C.
historicalPeakIndustrialPeriod
Indicates the time period during which an entity reached its highest level of industrial activity or development.
-
D.
modernizationPeriod
Indicates the time span during which an entity undergoes or is subject to modernization efforts or processes.
-
E.
navalEra
Indicates the historical period or era in which a naval-related event, activity, or condition takes place.
- 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_69ca842e9dcc8190a264119e683cfe04 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd50bc94108190a1b8146a78166009 |
completed | April 1, 2026, 5:07 p.m. |
| PD | Predicate disambiguation | batch_69cca53bd6ec81909bf403ce304e5c08 |
completed | April 1, 2026, 4:55 a.m. |
Created at: March 30, 2026, 7:44 p.m.