Triple
T38645300
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Huntsman Altimor |
E938698
|
entity |
| Predicate | primaryRoleInEncounter |
P186807
|
FINISHED |
| Object | ranged physical damage dealer |
—
|
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: ranged physical damage dealer | Statement: [Huntsman Altimor, primaryRoleInEncounter, ranged physical damage dealer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryRoleInEncounter Context triple: [Huntsman Altimor, primaryRoleInEncounter, ranged physical damage dealer]
-
A.
teamRoleInEncounters
chosen
Indicates the specific role an entity holds within a team during particular encounters or interactions.
-
B.
primaryRoleFor
Indicates that one entity serves as the main or most important role or function for another entity.
-
C.
principalRoleIn
Indicates that an entity holds the primary or leading role in a particular context, activity, or relationship.
-
D.
clinicalRole
Indicates the specific function, responsibility, or position an entity holds within a clinical or healthcare context.
-
E.
primaryPatientType
Indicates the main category or classification of patient that is primarily associated with or targeted by an entity, action, or service.
- 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_69f76ed948ec81908ce7811608a8f359 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c9141dc819098d7fcc36e69882c |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a2026248190b894436a578d79ac |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:32 p.m.