Triple
T26638538
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Documentum |
E668704
|
entity |
| Predicate | acquisitionDateByOpenText |
P2754
|
FINISHED |
| Object | 2017 |
—
|
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: 2017 | Statement: [Documentum, acquisitionDateByOpenText, 2017]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: acquisitionDateByOpenText Context triple: [Documentum, acquisitionDateByOpenText, 2017]
-
A.
acquisitionDate
chosen
Indicates the date on which one entity formally acquires or takes ownership of another entity.
-
B.
lineBOpeningDate
Indicates the date on which line B was officially opened or began operation.
-
C.
openingDateAsThroughLine
Indicates that the opening date is used as a continuous reference or organizing thread linking related events, records, or states over time.
-
D.
dateOfTextualForm
Indicates the date associated with the creation, writing, or specific textual version of a work or document.
-
E.
accessionDate
Indicates the date on which an item, record, or entity was formally added to a collection, system, or repository.
- 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_69ee9d0024b8819090a7c8cf669a3b6c |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f6383625cc8190aa223d8ef655743c |
completed | May 2, 2026, 5:45 p.m. |
| PD | Predicate disambiguation | batch_69f63709e4848190b5cf322e06b23fb6 |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 27, 2026, 2:28 a.m.