Triple
T29287548
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Celanese Corporation |
E742558
|
entity |
| Predicate | reincorporatedIn |
P29463
|
FINISHED |
| Object | United States |
—
|
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: United States | Statement: [Celanese Corporation, reincorporatedIn, United States]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reincorporatedIn Context triple: [Celanese Corporation, reincorporatedIn, United States]
-
A.
reincorporated
chosen
Indicates that an entity has been formed again or brought back into existence as a corporation after having previously ceased or changed its corporate status.
-
B.
reincorporationByForce
Indicates the forced reabsorption or reuniting of an entity into a larger entity or former whole against its will.
-
C.
laterIncorporatedInto
Indicates that one entity was subsequently merged into, absorbed by, or formally made part of another entity at a later time.
-
D.
reintegratedInto
Indicates that an entity has been brought back and incorporated again into a group, system, or context it was previously separated from.
-
E.
incorporatedAs
Indicates that an organization has been legally formed and registered under a specific corporate structure or name.
- 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_69f09121ed8c8190b4cb27be3619c262 |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69f6653ccf648190b65fb1141928e47e |
completed | May 2, 2026, 8:57 p.m. |
| PD | Predicate disambiguation | batch_69f660f2e3708190ab658652bcfc04d0 |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 28, 2026, 12:59 p.m.