Triple
T38588854
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Festergut |
E932406
|
entity |
| Predicate | roleInEncounter |
P186807
|
FINISHED |
| Object | tank-and-spank with heavy raid damage |
—
|
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: tank-and-spank with heavy raid damage | Statement: [Festergut, roleInEncounter, tank-and-spank with heavy raid damage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInEncounter Context triple: [Festergut, roleInEncounter, tank-and-spank with heavy raid damage]
-
A.
teamRoleInEncounters
chosen
Indicates the specific role an entity holds within a team during particular encounters or interactions.
-
B.
roleInAppointments
Indicates the specific function or capacity an entity holds within one or more scheduled appointments.
-
C.
hasPatientRole
Indicates that an entity participates in a relationship or activity specifically in the role of a patient (the one receiving care, treatment, or action).
-
D.
clinicalRole
Indicates the specific function, responsibility, or position an entity holds within a clinical or healthcare context.
-
E.
roleInIncident
Indicates the specific function, capacity, or involvement an entity has within a particular incident or event.
- 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_69f76ec654d48190b421111cf26e54d9 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a0340784c488190aa6c7c9be2e8a434 |
completed | May 12, 2026, 3 p.m. |
| PD | Predicate disambiguation | batch_6a033f33eddc819091507716f6ed7d7d |
completed | May 12, 2026, 2:54 p.m. |
Created at: May 3, 2026, 4:32 p.m.