Triple
T4219391
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rohm and Haas |
E94301
|
entity |
| Predicate | stockExchangeListingStatus |
P45352
|
FINISHED |
| Object | formerly publicly traded |
—
|
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: formerly publicly traded | Statement: [Rohm and Haas, stockExchangeListingStatus, formerly publicly traded]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stockExchangeListingStatus Context triple: [Rohm and Haas, stockExchangeListingStatus, formerly publicly traded]
-
A.
stockExchangeStatus
Indicates the operational or trading condition of a stock exchange at a given time (e.g., open, closed, halted).
-
B.
stockExchangeListingSuccessor
Indicates that one entity has succeeded or replaced another in being listed on a particular stock exchange.
-
C.
usedByStockExchange
Indicates that something (such as a system, standard, or instrument) is utilized or adopted by a stock exchange in its operations or services.
-
D.
issuerListingStatus
chosen
Indicates the current listing state or eligibility of an issuer’s securities on a trading venue or exchange.
-
E.
hasStockExchange
Indicates that an entity is associated with or listed on a particular stock exchange.
- 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_69b3451997e08190851db4a9a588837d |
completed | March 12, 2026, 10:58 p.m. |
| NER | Named-entity recognition | batch_69b34e4bf6088190926b982039a12079 |
completed | March 12, 2026, 11:37 p.m. |
| PD | Predicate disambiguation | batch_69b347f1d7b48190bd8974c03c7dc937 |
completed | March 12, 2026, 11:10 p.m. |
Created at: March 12, 2026, 11:04 p.m.