Triple
T4446571
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DowDuPont |
E96302
|
entity |
| Predicate | spinOffEffectiveDate |
P2753
|
FINISHED |
| Object | 2019-04-01 |
—
|
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: 2019-04-01 | Statement: [DowDuPont, spinOffEffectiveDate, 2019-04-01]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spinOffEffectiveDate Context triple: [DowDuPont, spinOffEffectiveDate, 2019-04-01]
-
A.
spinOffDate
chosen
Indicates the date on which an entity was formally separated or spun off from another entity.
-
B.
spinOff
Indicates that a new entity is created by separating or divesting part of an existing entity, forming an independent offshoot derived from the original.
-
C.
surrenderEffectiveTime
Indicates the point in time at which a surrender (e.g., of rights, ownership, or an agreement) becomes legally or practically effective.
-
D.
extensionEffectiveDate
Indicates the date on which an extension to an existing agreement, term, or condition becomes effective.
-
E.
holdingDate
Indicates the date on which a holding, possession, or ownership of something is recorded or takes effect.
- 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_69b345415ba481908df738e7174448ba |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b355d1eba08190899d0a3c1684ce4e |
completed | March 13, 2026, 12:09 a.m. |
| PD | Predicate disambiguation | batch_69b34f62c180819097ced38da2052207 |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:32 p.m.