Triple
T28788640
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sandra Stansfield |
E726887
|
entity |
| Predicate | taughtBreathingMethodBy |
P165587
|
FINISHED |
| Object | Dr. Emlyn McCarron |
—
|
NE NERFINISHED |
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: Dr. Emlyn McCarron | Statement: [Sandra Stansfield, taughtBreathingMethodBy, Dr. Emlyn McCarron]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: taughtBreathingMethodBy Context triple: [Sandra Stansfield, taughtBreathingMethodBy, Dr. Emlyn McCarron]
-
A.
breathingType
Indicates the specific manner or pattern in which an entity breathes (e.g., type or mode of respiration).
-
B.
breathRegulationComponent
Indicates a component that participates in or contributes to the regulation or control of breathing.
-
C.
breathingBehavior
Indicates how an entity performs the act of breathing, such as its pattern, rate, or style of respiration.
-
D.
breathingAdaptation
Indicates an adaptation that modifies or optimizes how an organism breathes in response to its environment or physiological demands.
-
E.
canBreathe
Indicates that an entity has the ability to inhale and exhale air (or another medium) to sustain respiration.
- 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_69f0319aabec81908368720196f69a35 |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f6596b210481908af6cd555748f75b |
completed | May 2, 2026, 8:07 p.m. |
| PD | Predicate disambiguation | batch_69f65760fd3081908ffe014a5e2bf069 |
completed | May 2, 2026, 7:58 p.m. |
| PDg | Predicate description generation | batch_69f658ebeca4819096beb3f98f73fe31 |
completed | May 2, 2026, 8:05 p.m. |
Created at: April 28, 2026, 6:22 a.m.