Triple
T30740510
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HRCtee |
E782677
|
entity |
| Predicate | hasProcedures |
P201580
|
FINISHED |
| Object | State reporting procedure |
—
|
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: State reporting procedure | Statement: [HRCtee, hasProcedures, State reporting procedure]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasProcedures Context triple: [HRCtee, hasProcedures, State reporting procedure]
-
A.
hasSpecialProcedure
Indicates that a particular entity is associated with or governed by a designated special procedure or process.
-
B.
hadProcedure
Indicates that a subject underwent or received a specific medical or clinical procedure.
-
C.
hasCheckInProcedure
Indicates that there is a defined process or set of steps required for an entity to check in or be checked in.
-
D.
hasSurgery
Indicates that a surgical procedure is performed on or undergone by an entity.
-
E.
providesProcedure
Indicates that one entity supplies, makes available, or performs a specific procedure for another entity.
- 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_69f224aeb1588190897d395e8ed2acb8 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a0008225cc081909ff1fd0639859dc4 |
completed | May 10, 2026, 4:22 a.m. |
| PD | Predicate disambiguation | batch_6a0007bac5d8819098aff8031d4abe5d |
completed | May 10, 2026, 4:21 a.m. |
| PDg | Predicate description generation | batch_6a000821b12c819093ca3b3dc0cff370 |
completed | May 10, 2026, 4:22 a.m. |
Created at: April 29, 2026, 8:37 p.m.