Triple
T8245142
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DD |
E192832
|
entity |
| Predicate | issuerKnownFor |
P48658
|
FINISHED |
| Object | industrial chemicals |
—
|
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: industrial chemicals | Statement: [DD, issuerKnownFor, industrial chemicals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: issuerKnownFor Context triple: [DD, issuerKnownFor, industrial chemicals]
-
A.
issuerAlsoKnownFor
Indicates that the issuer is additionally recognized or notable for another role, activity, or attribute beyond their primary identified capacity.
-
B.
issuerType
Indicates the classification or category of the entity that issues something (such as a document, credential, or instrument).
-
C.
issuerBestKnownFor
chosen
Indicates the primary work, achievement, or characteristic for which an issuer is most widely recognized.
-
D.
issuerFounded
Indicates that one entity is the organization or person that established or created the other entity at its founding.
-
E.
issuerProduces
Indicates that an issuer creates, generates, or brings into existence a particular product, document, asset, or item.
- 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_69ca82de7b8c81908d8106f8a53cff9b |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb7872f6d481909ea1d3c2aad1a2b1 |
completed | March 31, 2026, 7:32 a.m. |
| PD | Predicate disambiguation | batch_69cb36b437e881909958591357e83b9d |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:48 p.m.