Triple
T26862556
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coltness Iron Works |
E676370
|
entity |
| Predicate | majorPeriodOfActivity |
P18555
|
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: [Coltness Iron Works, majorPeriodOfActivity, 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: majorPeriodOfActivity Context triple: [Coltness Iron Works, majorPeriodOfActivity, 19th century]
-
A.
majorActivity
Indicates that the related entity performs, participates in, or is primarily associated with a main or most significant activity.
-
B.
periodOfMajorUse
Indicates the time span during which something was primarily or most intensively used.
-
C.
historicalPeriodOfMajorActivity
chosen
Indicates the historical period during which an entity carried out its most significant or influential activities.
-
D.
timePeriodOfLife
Indicates the span or phase of time during which an entity exists, lives, or is active.
-
E.
primaryFunctionInPeriod
Indicates that an entity serves as the main or most important function or role of another entity during a specified time period.
- 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_69eee9ba94bc8190b44c5d4397d04ecd |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f7805ce6208190ac6dbd9c97989978 |
completed | May 3, 2026, 5:05 p.m. |
| PD | Predicate disambiguation | batch_69f77956ec648190ba4fb7e9d83fd107 |
completed | May 3, 2026, 4:35 p.m. |
Created at: April 27, 2026, 5:26 a.m.