Triple
T30389277
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | second-generation Grubbs catalyst |
E773027
|
entity |
| Predicate | moreActiveThan |
P160217
|
FINISHED |
| Object | first-generation Grubbs catalyst |
—
|
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: first-generation Grubbs catalyst | Statement: [second-generation Grubbs catalyst, moreActiveThan, first-generation Grubbs catalyst]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: moreActiveThan Context triple: [second-generation Grubbs catalyst, moreActiveThan, first-generation Grubbs catalyst]
-
A.
lessActiveThan
Indicates that one entity exhibits a lower level of activity or engagement compared to another entity.
-
B.
activeWith
Indicates that an entity is currently engaged in or functioning together with another specified entity.
-
C.
activeAs
Indicates that an entity is currently functioning or serving in a particular role, capacity, or status.
-
D.
largerThan
Indicates that one entity has a greater size, extent, or magnitude than another entity.
-
E.
moreIntenseThan
chosen
Indicates that one entity exhibits a greater degree or strength of a particular quality, effect, or activity than another entity.
- 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_69f2248ef0a48190aa54d4d8ac3e5758 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6859ae6bc81909486430ab7eaef48 |
completed | May 2, 2026, 11:15 p.m. |
| PD | Predicate disambiguation | batch_69f678d019fc8190913662cd2f87b857 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 29, 2026, 8:02 p.m.