Triple
T32220573
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Idar-Oberstein |
E823051
|
entity |
| Predicate | hasIndustryHistorySince |
P3008
|
FINISHED |
| Object | 15th century |
—
|
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: 15th century | Statement: [Idar-Oberstein, hasIndustryHistorySince, 15th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasIndustryHistorySince Context triple: [Idar-Oberstein, hasIndustryHistorySince, 15th century]
-
A.
hasHistoricIndustry
chosen
Indicates that an entity has been associated with a notable or historically significant industry or industrial activity in the past.
-
B.
hadStateOwnershipOfIndustry
Indicates that a governing authority or state entity possessed ownership and control over a particular industry.
-
C.
hasProductionHistory
Indicates that an entity is associated with a record or account of its past production activities, processes, or outputs.
-
D.
hasMajorEmployerHistory
Indicates that an entity has a documented history of employment with a major or significant employer.
-
E.
hasLongHistory
Indicates that the relationship or subject has existed or persisted over a long period of time.
- 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_69f3490b4f948190b99e4f999f5be25f |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69ff891e4b9c8190aa86a339a8944496 |
completed | May 9, 2026, 7:21 p.m. |
| PD | Predicate disambiguation | batch_69ff8801180c8190b23e20996ca68e0a |
completed | May 9, 2026, 7:16 p.m. |
Created at: May 1, 2026, 12:38 a.m.