Triple
T27741591
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Diels–Alder reaction |
E701868
|
entity |
| Predicate | endoPreference |
P163178
|
FINISHED |
| Object | secondary orbital interactions |
—
|
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: secondary orbital interactions | Statement: [Diels–Alder reaction, endoPreference, secondary orbital interactions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: endoPreference Context triple: [Diels–Alder reaction, endoPreference, secondary orbital interactions]
-
A.
unitPreference
Indicates a relationship where one entity specifies or favors a particular unit of measurement or representation over others.
-
B.
statedPreference
Indicates that one entity has explicitly expressed or declared a preference for another entity or option.
-
C.
typicalPolicyPreference
Indicates that one entity’s policy preference is characteristic or representative of what is usually favored by another entity or group.
-
D.
armorPreference
Indicates a character’s favored type or style of armor they typically choose to wear or use.
-
E.
currentPreference
Indicates the option, choice, or setting that an entity presently favors over alternatives at this moment in time.
- 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_69ef6a53c7388190899baa6daf42301c |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f637169d6c8190bf74d5b882d2eb7d |
completed | May 2, 2026, 5:40 p.m. |
| PD | Predicate disambiguation | batch_69f63188e7408190af8ce8b93d128c63 |
completed | May 2, 2026, 5:16 p.m. |
| PDg | Predicate description generation | batch_69f6352df6148190bc10772cd40bd7b3 |
completed | May 2, 2026, 5:32 p.m. |
Created at: April 27, 2026, 4:11 p.m.