Triple
T21727119
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lustenau |
E536300
|
entity |
| Predicate | hasIndustryHistoryPeriod |
P58089
|
FINISHED |
| Object | 19th century textile boom |
—
|
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: 19th century textile boom | Statement: [Lustenau, hasIndustryHistoryPeriod, 19th century textile boom]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasIndustryHistoryPeriod Context triple: [Lustenau, hasIndustryHistoryPeriod, 19th century textile boom]
-
A.
hasHistoricIndustry
Indicates that an entity has been associated with a notable or historically significant industry or industrial activity in the past.
-
B.
hasHistoryPeriod
chosen
Indicates that something is associated with, belongs to, or occurs within a specific historical period or era.
-
C.
hasProductionHistory
Indicates that an entity is associated with a record or account of its past production activities, processes, or outputs.
-
D.
hadStateOwnershipOfIndustry
Indicates that a governing authority or state entity possessed ownership and control over a particular industry.
-
E.
hasHistoricalData
Indicates that an entity possesses recorded information or records about past events, states, or values relevant to it.
- 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_69e0c46d3284819099a4f9d5a704eb95 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69efd973ac648190bb09e20ac1be2d9b |
completed | April 27, 2026, 9:47 p.m. |
| PD | Predicate disambiguation | batch_69e6969725bc81908e7ad19619ba2688 |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:48 p.m.