Triple
T33187672
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ENR |
E849516
|
entity |
| Predicate | hasUnderlyingParentOrigin |
P3654
|
FINISHED |
| Object | spin-off from Siemens AG |
—
|
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: spin-off from Siemens AG | Statement: [ENR, hasUnderlyingParentOrigin, spin-off from Siemens AG]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasUnderlyingParentOrigin Context triple: [ENR, hasUnderlyingParentOrigin, spin-off from Siemens AG]
-
A.
hasParentAccordingToSource
Indicates that an entity is recorded as the parent of another entity according to a specified source or authority.
-
B.
hasUnderlyingWebsite
Indicates that one entity is supported, represented, or implemented by another entity that functions as its underlying website.
-
C.
hasVendorOrigin
Indicates that something originates from, or is supplied by, a particular vendor.
-
D.
hasOriginIn
chosen
Indicates that something begins, arises, or is derived from a specified source, place, or cause.
-
E.
hasPrimaryVisitorOrigin
Indicates that an entity’s main or most common source location of its visitors is a specified place.
- 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_69f3495e0f108190a6a7006f79f9c2c3 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fbc36ce1f88190a7fa1656b714e107 |
completed | May 6, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69fbbd13595c81908719f52c3d37a7e8 |
completed | May 6, 2026, 10:13 p.m. |
Created at: May 1, 2026, 1:29 a.m.