Triple
T26074161
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Adams catalyst |
E657633
|
entity |
| Predicate | isHeterogeneous |
P159920
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Adams catalyst, isHeterogeneous, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isHeterogeneous Context triple: [Adams catalyst, isHeterogeneous, true]
-
A.
isHomogeneous
Indicates that all elements or parts involved share the same type, nature, or characteristics, without significant variation among them.
-
B.
hasHigherVariety
Indicates that one entity offers or contains a greater diversity or range of items, types, or options than another entity.
-
C.
hasMultiple
Indicates that an entity is associated with more than one instance or occurrence of another related entity.
-
D.
isComposite
Indicates that an entity is made up of multiple components or parts combined into a single whole.
-
E.
hasVarietyOf
Indicates that an entity possesses or offers multiple different types, forms, or versions of something.
- 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_69ee5bbe539081909efc7f9dd7c1b53c |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f606cde3608190a83c0f258d8b38b7 |
completed | May 2, 2026, 2:14 p.m. |
| PD | Predicate disambiguation | batch_69f5aff889988190ad10bcf1a280f717 |
completed | May 2, 2026, 8:04 a.m. |
| PDg | Predicate description generation | batch_69f5f6b32a8881909baa0db57b80d56a |
completed | May 2, 2026, 1:05 p.m. |
Created at: April 26, 2026, 7:32 p.m.