Triple
T24386756
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Poulnabrone dolmen |
E614768
|
entity |
| Predicate | numberOfHumanRemainsFound |
P156012
|
FINISHED |
| Object | over 30 individuals |
—
|
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: over 30 individuals | Statement: [Poulnabrone dolmen, numberOfHumanRemainsFound, over 30 individuals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfHumanRemainsFound Context triple: [Poulnabrone dolmen, numberOfHumanRemainsFound, over 30 individuals]
-
A.
numberOfUnidentifiedRemains
Indicates the count of human remains that have not yet been identified in a given context or case.
-
B.
numberOfUnidentifiedBurials
Indicates the count of burial sites or graves where the interred individuals have not been identified.
-
C.
numberOfVictimsInMassGraves
Indicates the count of individuals who were killed and buried together in mass graves associated with a particular event or context.
-
D.
massGravesDiscovered
Indicates that previously unknown burial sites containing multiple bodies have been found.
-
E.
numberOfBonesRecovered
Indicates the count of bones that have been found and recovered in relation to a particular subject or event.
- F. None of above. chosen
Provenance (4 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_69e2d7e362e481909e32fe4ef8269d4f |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f29454c36c8190b7820dbf5af7b695 |
completed | April 29, 2026, 11:29 p.m. |
| PD | Predicate disambiguation | batch_69f287c4a2b48190b80fb7a3c0e9b018 |
completed | April 29, 2026, 10:35 p.m. |
| PDg | Predicate description generation | batch_69f28f4d978c81908310c01def2514cc |
completed | April 29, 2026, 11:07 p.m. |
Created at: April 18, 2026, 2:03 a.m.