Triple
T35677689
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Enso |
E1030908
|
entity |
| Predicate | notableCompanyNamedAfter |
P64362
|
FINISHED |
| Object | Enso-Gutzeit |
E1758657
|
NE 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: Enso-Gutzeit | Statement: [Enso, notableCompanyNamedAfter, Enso-Gutzeit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableCompanyNamedAfter Context triple: [Enso, notableCompanyNamedAfter, Enso-Gutzeit]
-
A.
hasCompanyNamedAfter
chosen
Indicates that one entity has a company whose name is derived from or identical to the other entity.
-
B.
notableCompanyFoundedIn
Indicates that a company is recognized as notable and was founded in the specified location or time period.
-
C.
notableEnterprise
Indicates that an entity is a business or commercial organization recognized for its significance, prominence, or impact.
-
D.
notableAsNamesakeOf
Indicates that one entity is recognized or distinguished specifically for being the namesake of another entity.
-
E.
notableCompanyHistory
Indicates that there exists a significant or historically important relationship or event involving the company and the subject entity.
- F. None of above.
Provenance (4 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_69f76e0bb6608190ad3a1880be54a17d |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a38728954388190b2631fe479f59f58 |
completed | June 21, 2026, 11:23 p.m. |
| PD | Predicate disambiguation | batch_6a037a04d8348190a4819666eab42c9b |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:05 p.m.