Triple
T625817
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Manhattan Company |
E15815
|
entity |
| Predicate | dissolvedByMerger |
P17851
|
FINISHED |
| Object | mid-20th century |
—
|
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: mid-20th century | Statement: [The Manhattan Company, dissolvedByMerger, mid-20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dissolvedByMerger Context triple: [The Manhattan Company, dissolvedByMerger, mid-20th century]
-
A.
foundedByMergerOf
Indicates that an entity was created through the merger or combination of two or more predecessor entities.
-
B.
dissolvedOrAbolished
Indicates that an organization, institution, or formal entity has been officially terminated, disbanded, or ceased to exist.
-
C.
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.
-
D.
mergerResult
Indicates that one or more entities have combined into a single entity, specifying the outcome or resulting entity of the merger.
-
E.
mergerType
Indicates the specific kind or category of merger relationship that exists between the involved entities.
- 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_69a4935c131c8190a5378c6bf101e8cc |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a49e574444819087999404f3e3ffd9 |
completed | March 1, 2026, 8:15 p.m. |
| PD | Predicate disambiguation | batch_69a49d0069d0819087c83b608f6fc053 |
completed | March 1, 2026, 8:09 p.m. |
| PDg | Predicate description generation | batch_69a49e2107548190af0c1d67cfa475d1 |
completed | March 1, 2026, 8:14 p.m. |
Created at: March 1, 2026, 7:35 p.m.