Triple
T2754122
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Edison Trust |
E61059
|
entity |
| Predicate | dissolvedFor |
P36898
|
FINISHED |
| Object | violation of antitrust law |
—
|
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: violation of antitrust law | Statement: [Edison Trust, dissolvedFor, violation of antitrust law]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dissolvedFor Context triple: [Edison Trust, dissolvedFor, violation of antitrust law]
-
A.
dissolved
Indicates that one substance has been mixed into another so thoroughly that it forms a uniform solution and is no longer distinguishable as a separate phase.
-
B.
dissolutionFollowedBy
Indicates that one dissolution event occurs first and is directly succeeded by another specified event or state.
-
C.
canBeDissolvedWith
Indicates that one entity is capable of being dissolved or broken down when exposed to another specified substance or medium.
-
D.
dissolutionTime
Indicates the point in time at which a relationship, structure, or entity ceases to exist or is formally terminated.
-
E.
dissolvedAfterEvent
chosen
Indicates that an entity ceased to exist, function, or remain intact as a direct consequence of a specified event occurring beforehand.
- 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_69ab4b7a85bc819094a349b84beb1f2c |
completed | March 6, 2026, 9:47 p.m. |
| NER | Named-entity recognition | batch_69abdb7073d081909da84b21015972f2 |
completed | March 7, 2026, 8:01 a.m. |
| PD | Predicate disambiguation | batch_69abd82d005c81908a1ac7a1313c6d88 |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:56 p.m.