Triple
T18425280
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bohr effect |
E442121
|
entity |
| Predicate | lessPronouncedIn |
P33999
|
FINISHED |
| Object | pulmonary capillaries |
—
|
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: pulmonary capillaries | Statement: [Bohr effect, lessPronouncedIn, pulmonary capillaries]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lessPronouncedIn Context triple: [Bohr effect, lessPronouncedIn, pulmonary capillaries]
-
A.
isMorePronouncedIn
chosen
Indicates that a particular feature, quality, or effect appears with greater intensity or prominence in one context, entity, or condition than in another.
-
B.
lessSevereIn
Indicates that one condition, event, or factor has a lower level of severity than another within a specified context.
-
C.
correctPronunciation
Indicates that one entity provides the accurate or standard way to pronounce another entity (such as a word or name).
-
D.
notFullyPhonetic
Indicates that the representation of a word or utterance does not capture all of its sounds in a strictly phonetic manner.
-
E.
lessWorthyThan
Indicates that one entity is considered to have lower value, merit, or worth compared to 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_69d8b9eb8a508190a942fd75ebd8b1dc |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e51b1149788190ad7c453547a6e07c |
completed | April 19, 2026, 6:12 p.m. |
| PD | Predicate disambiguation | batch_69e469bf7f74819096a01173493412c2 |
completed | April 19, 2026, 5:35 a.m. |
Created at: April 10, 2026, 10:47 a.m.