Triple
T28021797
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Karle |
E707706
|
entity |
| Predicate | hasNotableChemist |
P198485
|
FINISHED |
| Object | Jerome Karle |
—
|
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: Jerome Karle | Statement: [Karle, hasNotableChemist, Jerome Karle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableChemist Context triple: [Karle, hasNotableChemist, Jerome Karle]
-
A.
usesChemistry
Indicates that one entity applies or relies on chemistry, chemical methods, or chemical principles in relation to another entity or context.
-
B.
hasNotableDrug
Indicates that an entity is associated with a drug that is considered notable or significant in some recognized context.
-
C.
hasNotableComposer
Indicates that an entity is associated with a composer who is recognized as particularly significant or distinguished.
-
D.
hasNotableExpositor
Indicates that an entity has a person or source that is especially recognized for explaining, interpreting, or presenting it.
-
E.
notableCompound
Indicates that one entity is a chemical compound that is especially significant, well-known, or noteworthy in relation to the other entity.
- 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_69ef96baf3a881909a2b63844185dddd |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69feecf1bb248190ba30f0bb1d22ee08 |
completed | May 9, 2026, 8:14 a.m. |
| PD | Predicate disambiguation | batch_69feea5f27748190b223ee4e3ba5a678 |
completed | May 9, 2026, 8:03 a.m. |
| PDg | Predicate description generation | batch_69feecf102e08190b237c29e45beeca0 |
completed | May 9, 2026, 8:14 a.m. |
Created at: April 27, 2026, 8:10 p.m.