Triple
T505148
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Second Industrial Revolution |
E10487
|
entity |
| Predicate | hasKeyIndustry |
P3008
|
FINISHED |
| Object | steel industry |
—
|
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: steel industry | Statement: [Second Industrial Revolution, hasKeyIndustry, steel industry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasKeyIndustry Context triple: [Second Industrial Revolution, hasKeyIndustry, steel industry]
-
A.
hasPrincipalIndustry
Indicates that an entity’s main or primary industry of operation is the specified industry.
-
B.
hasHistoricIndustry
chosen
Indicates that an entity has been associated with a notable or historically significant industry or industrial activity in the past.
-
C.
hasKeyOrganization
Indicates that an entity is associated with or primarily represented by a main or primary organization.
-
D.
hasKeyWork
Indicates that an entity possesses or is associated with a primary or central work (such as a main publication, artwork, or project) that is especially representative or important.
-
E.
hasKeyAgency
Indicates that an entity serves as the primary responsible or controlling agency for another entity, action, or process.
- 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_69a2e848adf881908e5e04f7af030093 |
completed | Feb. 28, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69a2f14b2acc8190818e8a53eac69c54 |
completed | Feb. 28, 2026, 1:44 p.m. |
| PD | Predicate disambiguation | batch_69a2edfce7a08190a408bc019de60d5d |
completed | Feb. 28, 2026, 1:30 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.