Triple
T3647422
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kandos |
E77333
|
entity |
| Predicate | industrialPast |
P2411
|
FINISHED |
| Object | Portland cement manufacturing |
—
|
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: Portland cement manufacturing | Statement: [Kandos, industrialPast, Portland cement manufacturing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: industrialPast Context triple: [Kandos, industrialPast, Portland cement manufacturing]
-
A.
hasIndustrialHeritage
chosen
Indicates that an entity possesses or is associated with historically significant industrial sites, structures, or practices.
-
B.
modernIndustry
Indicates that an entity operates within or is characteristic of contemporary, technologically advanced industrial practices and sectors.
-
C.
historicalPeakIndustrialPeriod
Indicates the time period during which an entity reached its highest level of industrial activity or development.
-
D.
timePeriodOfIndustrialization
Indicates the time period during which a given entity underwent industrialization.
-
E.
hasIndustrialSector
Indicates that an entity is associated with, operates in, or belongs to a particular industrial sector or branch of economic activity.
- 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_69ad85de1b988190a45f8dbfebc806fc |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc38aa2388190bf1af926375e2433 |
completed | March 8, 2026, 6:44 p.m. |
| PD | Predicate disambiguation | batch_69adb8445b2c8190ab07f6ad4e010d0e |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:24 p.m.