Triple
T25360078
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Evans aldol reaction |
E635933
|
entity |
| Predicate | auxiliaryFeature |
P158815
|
FINISHED |
| Object | recyclable |
—
|
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: recyclable | Statement: [Evans aldol reaction, auxiliaryFeature, recyclable]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: auxiliaryFeature Context triple: [Evans aldol reaction, auxiliaryFeature, recyclable]
-
A.
targetFeature
Indicates that one entity is the specific feature, attribute, or characteristic that another entity is directed toward, focused on, or intended to affect.
-
B.
recognizedFeature
Indicates that a particular feature has been identified and acknowledged as present or valid in relation to an entity or context.
-
C.
secondaryFunction
Indicates that an entity has an additional, supporting role or purpose beyond its primary function.
-
D.
auxiliaryTo
Indicates that one entity serves as a supporting or helping element that assists or modifies the primary action or role of another entity.
-
E.
annexDFeature
Indicates that one entity includes or incorporates another entity as a feature defined or specified in Annex D.
- 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_69e75a9b7cf481909f2dcdfb37d95ca7 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f49e0441108190be510b7bf3a22cea |
completed | May 1, 2026, 12:35 p.m. |
| PD | Predicate disambiguation | batch_69f4806d93dc8190b9dff4c63186faff |
completed | May 1, 2026, 10:29 a.m. |
| PDg | Predicate description generation | batch_69f48b9058d081908ec9af261ee092e2 |
completed | May 1, 2026, 11:16 a.m. |
Created at: April 21, 2026, 1:36 p.m.