Triple
T25033019
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Andrew Handyside |
E626900
|
entity |
| Predicate | hasPartInEnterprise |
P10186
|
FINISHED |
| Object | production of railway station ironwork |
—
|
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: production of railway station ironwork | Statement: [Andrew Handyside, hasPartInEnterprise, production of railway station ironwork]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPartInEnterprise Context triple: [Andrew Handyside, hasPartInEnterprise, production of railway station ironwork]
-
A.
hasPartIn
chosen
Indicates that an entity participates in or plays a role within a larger event, process, or composite entity.
-
B.
companyInternalPartOf
Indicates that one company is an internal subdivision, unit, or component of another company within the same corporate structure.
-
C.
isPartOfIndustry
Indicates that one entity belongs to, operates within, or is categorized under a particular industry sector.
-
D.
hasPart
Indicates that one entity is a component, segment, or constituent part of another entity.
-
E.
isPartOfBusinessArea
Indicates that one entity belongs to, is included within, or falls under the scope of a particular business area.
- 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_69e2ff2a2c088190be513727ee8bfe78 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f606c79ad081908369605f72e65ca6 |
completed | May 2, 2026, 2:14 p.m. |
| PD | Predicate disambiguation | batch_69f602ce79ec8190b8336c2b9de18ac7 |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 18, 2026, 6:07 a.m.