Triple
T38496901
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fujitsu Siemens Computers |
E919718
|
entity |
| Predicate | ownerAfterReorganization |
P153138
|
FINISHED |
| Object | Fujitsu |
—
|
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: Fujitsu | Statement: [Fujitsu Siemens Computers, ownerAfterReorganization, Fujitsu]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ownerAfterReorganization Context triple: [Fujitsu Siemens Computers, ownerAfterReorganization, Fujitsu]
-
A.
ownerAfterRebranding
Indicates that an entity is the owner of another entity specifically after a rebranding event has taken place.
-
B.
ownerAfterRedevelopment
Indicates that an entity becomes the owner of something following a redevelopment process or event.
-
C.
ownershipAfterIntegration
chosen
Indicates that one entity holds ownership or control of another entity after a merger, acquisition, or integration process has been completed.
-
D.
roleAfterRefounding
Indicates the role or position an entity holds following the refounding or re-establishment of an organization, institution, or similar entity.
-
E.
ownershipChangedAfter
Indicates that the ownership of an entity became different at some point after a specified time or event.
- 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_69f76e9ddd4481908f8c04439d848f9d |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fd02680d948190a3463fb119ba8556 |
completed | May 7, 2026, 9:21 p.m. |
| PD | Predicate disambiguation | batch_69fcf89c69b4819082bbc564bd15137d |
completed | May 7, 2026, 8:39 p.m. |
Created at: May 3, 2026, 4:31 p.m.