Triple
T28380940
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Self (Marc Quinn) |
E718885
|
entity |
| Predicate | bloodCollectionMethod |
P164696
|
FINISHED |
| Object | incremental blood donations |
—
|
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: incremental blood donations | Statement: [Self (Marc Quinn), bloodCollectionMethod, incremental blood donations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bloodCollectionMethod Context triple: [Self (Marc Quinn), bloodCollectionMethod, incremental blood donations]
-
A.
sampleCollected
Indicates that a sample has been obtained or gathered from a source as part of a collection process.
-
B.
bloodTypeRelativeToSystemicVeins
Indicates the relationship between blood and the systemic veins in terms of its type, characteristics, or classification within that venous system.
-
C.
obtainsBloodFrom
Indicates that one entity receives or collects blood from another entity.
-
D.
bloodProduced
Indicates that one entity generates or produces blood for another entity or as a result of a process.
-
E.
bloodUsedFor
Indicates that blood is utilized or applied for a particular purpose, function, or process.
- 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_69eff6ee5afc8190bd7375a29f0cc6c6 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f64ee0c2788190a94a04ad1902fd5e |
completed | May 2, 2026, 7:22 p.m. |
| PD | Predicate disambiguation | batch_69f64caede108190a35cc7cbfead866f |
completed | May 2, 2026, 7:12 p.m. |
| PDg | Predicate description generation | batch_69f64e36c57c8190af09470a8d35512b |
completed | May 2, 2026, 7:19 p.m. |
Created at: April 28, 2026, 1:06 a.m.