Triple
T33510582
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Big Nurse |
E858229
|
entity |
| Predicate | representsToPatients |
P198530
|
FINISHED |
| Object | absolute authority |
—
|
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: absolute authority | Statement: [Big Nurse, representsToPatients, absolute authority]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: representsToPatients Context triple: [Big Nurse, representsToPatients, absolute authority]
-
A.
representedTo
Indicates that one entity formally acted on behalf of or served as the representative of another entity in a given context or interaction.
-
B.
patientPortrayedBy
Indicates that a patient is represented or depicted by a particular actor, model, or illustrative figure.
-
C.
isUsedForPatients
Indicates that something is employed or applied in the care, treatment, or management of patients.
-
D.
presentedTo
Indicates that something (such as an item, work, or information) was formally given, shown, or introduced by one party to another as the recipient.
-
E.
treatsPatientsFrom
Indicates that a healthcare provider gives medical treatment or services to patients originating from a particular location or group.
- 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_69f3497721848190978fbee5e0a526f8 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fef112398081909237c3872345968b |
completed | May 9, 2026, 8:32 a.m. |
| PD | Predicate disambiguation | batch_69feefb14ec08190ab401987d8c84a23 |
completed | May 9, 2026, 8:26 a.m. |
| PDg | Predicate description generation | batch_69fef1112b0c8190a8eb027edb71e4e0 |
completed | May 9, 2026, 8:32 a.m. |
Created at: May 1, 2026, 1:38 a.m.