Triple
T28845501
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prince Dan of Yan |
E728442
|
entity |
| Predicate | hasAssassin |
P138555
|
FINISHED |
| Object | Jing Ke |
—
|
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: Jing Ke | Statement: [Prince Dan of Yan, hasAssassin, Jing Ke]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAssassin Context triple: [Prince Dan of Yan, hasAssassin, Jing Ke]
-
A.
hasAssassinCharacter
chosen
Indicates that an entity includes, features, or is associated with a character whose role or function is that of an assassin.
-
B.
hasAssassinationService
Indicates that one entity provides or is involved in carrying out assassination services for another entity.
-
C.
hasAccusedAssassin
Indicates that one entity has formally or informally claimed that another entity is the assassin responsible for a killing.
-
D.
hasKiller
Indicates that one entity is the killer or cause of death of another entity.
-
E.
hasKillerWeapon
Indicates that a particular weapon was used by an entity to commit a killing.
- 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_69f0319e8e7c8190b37288c8845b9dbc |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f6cee45590819086e489bfccbe4ac3 |
completed | May 3, 2026, 4:28 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1188708190b8f0f56e595e6057 |
completed | May 3, 2026, 4:16 a.m. |
Created at: April 28, 2026, 6:42 a.m.