Triple
T13064503
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clan Lamont |
E329284
|
entity |
| Predicate | massacreYearApprox |
P68809
|
FINISHED |
| Object | 1646 |
—
|
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: 1646 | Statement: [Clan Lamont, massacreYearApprox, 1646]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: massacreYearApprox Context triple: [Clan Lamont, massacreYearApprox, 1646]
-
A.
massacreYear
chosen
Indicates the year in which a massacre event took place.
-
B.
massacreOccurred
Indicates that a large-scale, deliberate killing of multiple individuals took place in a specific event or context.
-
C.
massacreAlsoKnownAs
Indicates that a particular massacre is known or referred to by an alternative name or names.
-
D.
significantMassacre
Indicates that a massacre event is of notable scale, impact, or historical importance relative to other such events.
-
E.
majorMassacre
Indicates a relationship where an event involves the large-scale, deliberate killing of many individuals, typically characterized by extreme violence and high casualty numbers.
- 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_69d80771749c81909a6d9197b9504872 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69d980e9bdfc81908eb90fb50597df64 |
completed | April 10, 2026, 10:59 p.m. |
| PD | Predicate disambiguation | batch_69d9803d46688190bac6b7d208f08d01 |
completed | April 10, 2026, 10:57 p.m. |
Created at: April 9, 2026, 8:59 p.m.