Triple
T24660775
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shropshire iron industry |
E610531
|
entity |
| Predicate | hasNotableIronmaster |
P157667
|
FINISHED |
| Object | Abraham Darby II |
—
|
NE NERFINISHED |
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: Abraham Darby II | Statement: [Shropshire iron industry, hasNotableIronmaster, Abraham Darby II]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableIronmaster Context triple: [Shropshire iron industry, hasNotableIronmaster, Abraham Darby II]
-
A.
hasNotableIronmaster
chosen
Indicates that an entity is associated with a notable ironmaster, typically as a place where they worked, lived, or held significant influence.
-
B.
hasNotableMine
Indicates that an entity possesses or is associated with a mine considered significant or noteworthy in some context.
-
C.
hasNotableWeaponNamedAfter
Indicates that an entity possesses a notable weapon that is named after another specific entity.
-
D.
hasNotableCraft
Indicates that an entity is associated with a particularly significant or distinguished craft, skill, or artisanal practice.
-
E.
operatedAsIronworksUntil
Indicates that an entity functioned in the capacity of an ironworks up to a specified point in 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_69e2c4d453248190a020354e93ef6282 |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f453035f508190be83a3d521723acf |
completed | May 1, 2026, 7:15 a.m. |
| PD | Predicate disambiguation | batch_69f44d6ef33081908f5d36ba1ae5f473 |
completed | May 1, 2026, 6:51 a.m. |
Created at: April 18, 2026, 2:34 a.m.