Triple
T38589700
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Razorgore the Untamed |
E932424
|
entity |
| Predicate | followedByEncounter |
P200139
|
FINISHED |
| Object | Vaelastrasz the Corrupt |
—
|
NE NERFINISHED |
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: Vaelastrasz the Corrupt | Statement: [Razorgore the Untamed, followedByEncounter, Vaelastrasz the Corrupt]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: followedByEncounter Context triple: [Razorgore the Untamed, followedByEncounter, Vaelastrasz the Corrupt]
-
A.
followsEncounter
chosen
Indicates that one encounter occurs after and in sequence with another encounter.
-
B.
hasEncounter
Indicates that one entity experiences or comes into contact with another entity or event, typically in a specific context or situation.
-
C.
endedFollowing
Indicates that one entity stopped following or subscribing to another entity after previously doing so.
-
D.
followedByMedicalTreatmentAt
Indicates that one event, condition, or action is succeeded in time by receiving medical treatment at a specific healthcare facility or provider.
-
E.
followedByInContext
Indicates that one element directly succeeds another within a specific contextual sequence or ordering.
- 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_69ffada24d188190a576a02dc280a7fb |
completed | May 9, 2026, 9:56 p.m. |
| PD | Predicate disambiguation | batch_69ffad46d6ac819081772f408b1389d5 |
completed | May 9, 2026, 9:55 p.m. |
Created at: May 3, 2026, 4:32 p.m.