Triple
T27731246
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | X/Open Company Limited |
E697434
|
entity |
| Predicate | activitySucceededBy |
P169572
|
FINISHED |
| Object | The Open Group |
—
|
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: The Open Group | Statement: [X/Open Company Limited, activitySucceededBy, The Open Group]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: activitySucceededBy Context triple: [X/Open Company Limited, activitySucceededBy, The Open Group]
-
A.
activityEndedBecauseOf
Indicates that an activity has come to an end specifically due to a particular cause, condition, or event.
-
B.
associatedActivity
Indicates that one entity is linked to, involved in, or characterized by a particular activity or set of activities.
-
C.
officeSucceededBy
Indicates that one office or position is followed or replaced by another office or position in a succession sequence.
-
D.
activityTime
Indicates the time period during which an activity occurs or is scheduled to take place.
-
E.
hasActivityIn
Indicates that an entity engages in or performs a particular activity within a specified context, location, or domain.
- F. None of above. chosen
Provenance (4 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_69ef590c3e288190ad54d2465af8ca4e |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f67fc237608190b6542b56038a7fe4 |
completed | May 2, 2026, 10:50 p.m. |
| PD | Predicate disambiguation | batch_69f67e3ed894819094c067c1ef624951 |
completed | May 2, 2026, 10:44 p.m. |
| PDg | Predicate description generation | batch_69f67f0353c88190a05b2db449abe0f4 |
completed | May 2, 2026, 10:47 p.m. |
Created at: April 27, 2026, 3:11 p.m.