Triple
T28970208
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Matewan Massacre |
E734249
|
entity |
| Predicate | numberOfDeadApproximate |
P150701
|
FINISHED |
| Object | 10 |
—
|
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: 10 | Statement: [Matewan Massacre, numberOfDeadApproximate, 10]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfDeadApproximate Context triple: [Matewan Massacre, numberOfDeadApproximate, 10]
-
A.
killedApproximate
Indicates that one entity caused the death of another, but the information about this killing is uncertain, estimated, or not known with exact precision.
-
B.
mineCountApproximate
Indicates that the number of mines associated with an entity is estimated or roughly counted rather than known exactly.
-
C.
junctionCountApprox
Indicates an approximate count of junctions or connection points involved in or associated with the given entities.
-
D.
hasApproximateCountInHumans
Indicates that an entity is associated with an estimated or approximate numerical count specifically in humans.
-
E.
hasApproximateNumberOfVictims
chosen
Indicates that an entity is associated with an estimated, non-exact count of victims.
- 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_69f05b0d1e7c819092baab93d3fe277e |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69ffb82be8148190a1c870d467a28c80 |
completed | May 9, 2026, 10:41 p.m. |
| PD | Predicate disambiguation | batch_69ffb7bbd550819094052e9a0d0ae320 |
completed | May 9, 2026, 10:39 p.m. |
Created at: April 28, 2026, 9:05 a.m.