Triple
T18088032
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Atrioventricular node |
E432889
|
entity |
| Predicate | typicalDelay |
P130384
|
FINISHED |
| Object | about 0.1 seconds |
—
|
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: about 0.1 seconds | Statement: [Atrioventricular node, typicalDelay, about 0.1 seconds]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalDelay Context triple: [Atrioventricular node, typicalDelay, about 0.1 seconds]
-
A.
typicalDelivery
Indicates the usual or standard way in which something is delivered, reflecting the most common delivery method or pattern in that context.
-
B.
typicalTimes
Indicates the usual or characteristic times at which an event, activity, or condition typically occurs.
-
C.
delayedBy
Indicates that one event, process, or action occurs later than expected or planned due to the influence or interference of another factor or entity.
-
D.
typicalDurationDays
Indicates the usual or expected number of days that an associated event, process, or state typically lasts.
-
E.
delayed
Indicates that an expected event, action, or outcome occurred later than its scheduled or usual 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_69d8b907d05c819083cc3bd6021089e6 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4dd16234c8190b547e893a829d6c5 |
completed | April 19, 2026, 1:48 p.m. |
| PD | Predicate disambiguation | batch_69e4330e1f2881908b2506d47c48736b |
completed | April 19, 2026, 1:42 a.m. |
| PDg | Predicate description generation | batch_69e438f5ae2c8190b11dee46534fa5a9 |
completed | April 19, 2026, 2:07 a.m. |
Created at: April 10, 2026, 10:27 a.m.