Triple
T37873942
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Archimonde |
E944670
|
entity |
| Predicate | memberAlongside |
P190064
|
FINISHED |
| Object | Kil'jaeden |
—
|
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: Kil'jaeden | Statement: [Archimonde, memberAlongside, Kil'jaeden]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: memberAlongside Context triple: [Archimonde, memberAlongside, Kil'jaeden]
-
A.
memberSide
chosen
Indicates that an entity is a member or participant on a particular side or party within a relationship, group, or conflict.
-
B.
playedAlongside
Indicates that two or more entities participated together at the same time in a shared activity, performance, or event.
-
C.
appearsAlongside
Indicates that two entities are present or occur together in the same context, setting, or instance.
-
D.
memberFrom
Indicates that an entity is a member originating from, or associated with, a particular source, group, or location.
-
E.
recognizedAlongside
Indicates that two or more entities are acknowledged, identified, or honored together in the same context or occasion.
- 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_69f76eef55d481908ca6660b4b532550 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fddd373cdc8190be1b12e70e4deb1f |
completed | May 8, 2026, 12:55 p.m. |
| PD | Predicate disambiguation | batch_69fddc6915a88190ad41e379aa3ede13 |
completed | May 8, 2026, 12:51 p.m. |
Created at: May 3, 2026, 4:19 p.m.