Triple
T1680539
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Iron and Steel Act 1949 |
E36327
|
entity |
| Predicate | industryCovered |
P71
|
FINISHED |
| Object | iron 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: iron industry | Statement: [Iron and Steel Act 1949, industryCovered, iron industry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: industryCovered Context triple: [Iron and Steel Act 1949, industryCovered, iron industry]
-
A.
industryContext
Indicates the industry or sector within which an entity, activity, or relationship is situated or most relevant.
-
B.
industryCenter
Indicates that a location functions as a primary hub or focal point for industrial activity or production.
-
C.
businessBase
Indicates that one entity serves as the primary business foundation, core location, or main operational base for another entity.
-
D.
industryPerception
Indicates how an industry is viewed or regarded, typically in terms of reputation, trust, or overall public and stakeholder opinion.
-
E.
sector
chosen
Indicates that an entity operates in, belongs to, or is associated with a particular economic or industrial sector.
- 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_69a886139ed081909af0940aa9313512 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69aba644070c81908745b56d981fe273 |
completed | March 7, 2026, 4:15 a.m. |
| PD | Predicate disambiguation | batch_69aa61b57a6881909373af287ef24799 |
completed | March 6, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:29 p.m.