Triple
T36333346
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Imtech |
E894711
|
entity |
| Predicate | notableBuyerOfAssets |
P204828
|
FINISHED |
| Object | Royal BAM Group |
E1446726
|
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: Royal BAM Group | Statement: [Imtech, notableBuyerOfAssets, Royal BAM Group]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableBuyerOfAssets Context triple: [Imtech, notableBuyerOfAssets, Royal BAM Group]
-
A.
notableAsset
Indicates that an entity possesses or is associated with an asset that is particularly significant, prominent, or noteworthy in relation to it.
-
B.
notableExchange
Indicates a significant or noteworthy transfer, interaction, or trade occurring between two or more entities.
-
C.
notableForbesListing
Indicates that an entity has been recognized or included in a notable Forbes magazine list or ranking.
-
D.
couldBeAcquiredBy
Indicates that one entity is a potential target to be obtained, bought, or taken over by another entity.
-
E.
notableInvestor
Indicates that an entity is a significant or prominent investor in another entity, typically by virtue of investment size, influence, or reputation.
- F. None of above. chosen
Provenance (5 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_69f76e4dcf088190a6c3216c209cab52 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c92f03c8190ae2751270b195423 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a397d9b09bc8190a76ee1f70c473b5b |
completed | June 22, 2026, 6:23 p.m. |
| PD | Predicate disambiguation | batch_6a037a0a54cc8190868c1bfa1590d1a6 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c82f8c88190bd77a086023ac0e1 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:09 p.m.