Triple
T20723173
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clan MacDonald of Glencoe |
E509368
|
entity |
| Predicate | massacreVictims |
P36783
|
FINISHED |
| Object | members of Clan MacDonald of Glencoe |
—
|
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: members of Clan MacDonald of Glencoe | Statement: [Clan MacDonald of Glencoe, massacreVictims, members of Clan MacDonald of Glencoe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: massacreVictims Context triple: [Clan MacDonald of Glencoe, massacreVictims, members of Clan MacDonald of Glencoe]
-
A.
massacrePerpetrators
Indicates that the subject is responsible for carrying out or participating in a massacre against the object.
-
B.
numberOfVictimsKilled
Indicates the count of victims who were killed as a result of the referenced event or action.
-
C.
notableVictims
Indicates that the object is a person or group who is especially well-known or significant as a victim of the subject.
-
D.
mainVictims
chosen
Indicates that the related entities are the primary or principal targets harmed or affected by an action, event, or perpetrator.
-
E.
massacreAlsoKnownAs
Indicates that a particular massacre is known or referred to by an alternative name or names.
- 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_69e0b4c4cc648190b45fda6e2b20af56 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c1e59b2081909fb6c29cb5018bb4 |
completed | April 21, 2026, 12:16 a.m. |
| PD | Predicate disambiguation | batch_69e5c04b31248190b9b9d91b5cb854e3 |
completed | April 20, 2026, 5:57 a.m. |
Created at: April 16, 2026, 12:28 p.m.