Triple
T34789590
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Schwitzer |
E1002908
|
entity |
| Predicate | hasDerivedCompanyName |
P90896
|
FINISHED |
| Object | Schwitzer Corporation |
—
|
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: Schwitzer Corporation | Statement: [Schwitzer, hasDerivedCompanyName, Schwitzer Corporation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDerivedCompanyName Context triple: [Schwitzer, hasDerivedCompanyName, Schwitzer Corporation]
-
A.
hasCompanyName
chosen
Indicates that an entity is associated with or identified by a specific company name.
-
B.
underlyingCompanyFormerName
Indicates that the object is a former or previous legal name by which the underlying company (the subject) was known.
-
C.
hasParentCompany
Indicates that one company is owned or controlled by another company that serves as its parent organization.
-
D.
hasSubsequentNameChange
Indicates that an entity undergoes a later change to its name, resulting in a new official designation after the original.
-
E.
underwentNameChangeTo
Indicates that an entity previously known by one name has changed its name to the specified new name.
- 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_69f76db47d408190a24fc7164439ea2d |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69ff289541e0819096eeceb8e6332650 |
completed | May 9, 2026, 12:29 p.m. |
| PD | Predicate disambiguation | batch_69ff281ab1988190920f0443be9f10cc |
completed | May 9, 2026, 12:27 p.m. |
Created at: May 3, 2026, 3:59 p.m.