Triple
T18020974
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tricuspid valve |
E431114
|
entity |
| Predicate | worksInSeriesWith |
P129460
|
FINISHED |
| Object | pulmonary valve |
—
|
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 valve | Statement: [Tricuspid valve, worksInSeriesWith, pulmonary valve]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: worksInSeriesWith Context triple: [Tricuspid valve, worksInSeriesWith, pulmonary valve]
-
A.
partOfSeriesWith
Indicates that one entity is a member or installment within the same series as another entity, linking them as related parts of a larger sequence or collection.
-
B.
appearsInSeriesBy
Indicates that one entity (such as a work or character) is featured within a series that is created, authored, or produced by another entity.
-
C.
airedWithSeriesFrom
Indicates that one series was broadcast together or in conjunction with another series during its airing period.
-
D.
basedInSeries
Indicates that one entity is set, located, or primarily takes place within the narrative world or context of a particular series.
-
E.
appearsInSeries
Indicates that an entity is featured or occurs within a particular series.
- 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_69d8b904530081908bf341d842464856 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4b9c1c5f88190a059ce4f86f7ed36 |
completed | April 19, 2026, 11:17 a.m. |
| PD | Predicate disambiguation | batch_69e3f904b8048190add43883cd7cb191 |
completed | April 18, 2026, 9:35 p.m. |
| PDg | Predicate description generation | batch_69e42d8eefa88190a700c7c1b4213e46 |
completed | April 19, 2026, 1:19 a.m. |
Created at: April 10, 2026, 10:24 a.m.