Triple
T33381287
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moutier |
E854786
|
entity |
| Predicate | hasIndustrialTraditionSince |
P149688
|
FINISHED |
| Object | 19th 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: 19th century | Statement: [Moutier, hasIndustrialTraditionSince, 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasIndustrialTraditionSince Context triple: [Moutier, hasIndustrialTraditionSince, 19th century]
-
A.
hasIndustrialHeritage
Indicates that an entity possesses or is associated with historically significant industrial sites, structures, or practices.
-
B.
industrializedBy
Indicates that an entity has undergone industrial development or transformation as a result of actions carried out by another specified agent or process.
-
C.
historicalPeriodOfIndustrialUse
chosen
Indicates the historical time span during which an entity was used for industrial purposes.
-
D.
hasIronworks
Indicates that one entity possesses, contains, or is the site of an ironworks facility or operation.
-
E.
isEarlyIndustrialCentreOf
Indicates that a place functioned as an important center of early industrial activity for another specified region or context.
- 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_69f3496ca10c8190908640d18fa00832 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69ffe6e2eb688190a45fd2c6415cd86a |
completed | May 10, 2026, 2:01 a.m. |
| PD | Predicate disambiguation | batch_69ffe65939488190a35b9c2e9c7ad868 |
completed | May 10, 2026, 1:58 a.m. |
Created at: May 1, 2026, 1:35 a.m.