Triple
T22503401
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Altran |
E556330
|
entity |
| Predicate | acquisitionOfAricentCompletedOn |
P15703
|
FINISHED |
| Object | 2018 |
—
|
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: 2018 | Statement: [Altran, acquisitionOfAricentCompletedOn, 2018]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: acquisitionOfAricentCompletedOn Context triple: [Altran, acquisitionOfAricentCompletedOn, 2018]
-
A.
acquisitionCompletedYear
chosen
Indicates the calendar year in which an acquisition transaction was fully completed.
-
B.
acquisitionResultedIn
Indicates that an acquisition event led to a particular outcome, state, or consequence for the involved entities.
-
C.
laterAcquiredBy
Indicates that one entity was acquired by another entity at a later point in time, after some prior state or ownership.
-
D.
acquisitionAnnouncedBy
Indicates that an acquisition event was publicly announced by the specified announcing entity (such as a company or organization).
-
E.
acquiredCompany
Indicates that one entity has purchased and taken ownership or control of another company.
- 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_69e11e555edc81909ca803587dafd747 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15d5a01888190ba65a05616b63cbe |
completed | April 29, 2026, 1:22 a.m. |
| PD | Predicate disambiguation | batch_69e898be31448190be5ae7f5656f0497 |
completed | April 22, 2026, 9:45 a.m. |
Created at: April 16, 2026, 8:50 p.m.