Triple
T33090718
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Advanced Cardiovascular Life Support guidelines |
E846771
|
entity |
| Predicate | updatedOnSchedule |
P71451
|
FINISHED |
| Object | approximately every 5 years |
—
|
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: approximately every 5 years | Statement: [Advanced Cardiovascular Life Support guidelines, updatedOnSchedule, approximately every 5 years]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: updatedOnSchedule Context triple: [Advanced Cardiovascular Life Support guidelines, updatedOnSchedule, approximately every 5 years]
-
A.
updatedEvery
chosen
Indicates that something is refreshed or brought up to date at a regular, specified interval.
-
B.
updatedIn
Indicates that an entity has undergone a change or modification within a specified time period or version context.
-
C.
rescheduledTo
Indicates that an event or action has been moved from its original time to a new specified time.
-
D.
updated
Indicates that an entity has been modified or brought to a more recent state compared to its previous version or status.
-
E.
isOnScheduleOf
Indicates that something is included in and follows the planned timing or sequence defined by a particular schedule.
- 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_69f3495590dc8190aa04f3dec74ce976 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6db6af1d88190989810182354d60f |
completed | May 3, 2026, 5:21 a.m. |
| PD | Predicate disambiguation | batch_69f6d82d068c8190940a3200ed760e38 |
completed | May 3, 2026, 5:07 a.m. |
Created at: May 1, 2026, 1:26 a.m.