Triple
T31748826
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AlliedSignal |
E810350
|
entity |
| Predicate | postMergerName |
P131799
|
FINISHED |
| Object | Honeywell International Inc. |
—
|
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: Honeywell International Inc. | Statement: [AlliedSignal, postMergerName, Honeywell International Inc.]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: postMergerName Context triple: [AlliedSignal, postMergerName, Honeywell International Inc.]
-
A.
postMergerCEO
Indicates that an individual serves as the chief executive officer of a company after it has undergone a merger.
-
B.
postMergerStatus
Indicates the status or condition of an entity following the completion of a merger.
-
C.
postMergerSuccessor
chosen
Indicates that one entity is the legal or organizational successor of another entity following a merger.
-
D.
postShowName
Indicates that an entity is associated with the name or title of a show that is displayed or used after the main show content (e.g., in post-show materials or contexts).
-
E.
postAmendmentName
Indicates the name or designation an entity has after an amendment or modification has been applied.
- 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_69f348e233cc819083b6695f70cd75d8 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6ab51508881908abb417ec8e196dd |
completed | May 3, 2026, 1:56 a.m. |
| PD | Predicate disambiguation | batch_69f6aa20a1588190a53533fc9764efb2 |
completed | May 3, 2026, 1:51 a.m. |
Created at: April 30, 2026, 11:27 p.m.