Triple
T13506128
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St Leonard’s Church ossuary |
E321018
|
entity |
| Predicate | estimatedNumberOfSkulls |
P110023
|
FINISHED |
| Object | over 1,000 |
—
|
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 1,000 | Statement: [St Leonard’s Church ossuary, estimatedNumberOfSkulls, over 1,000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: estimatedNumberOfSkulls Context triple: [St Leonard’s Church ossuary, estimatedNumberOfSkulls, over 1,000]
-
A.
numberOfColossalHeads
Indicates the quantity of colossal heads associated with or attributed to a given subject.
-
B.
numberOfBonesRecovered
Indicates the count of bones that have been found and recovered in relation to a particular subject or event.
-
C.
hasSkull
Indicates that an entity possesses or is characterized by the presence of a skull.
-
D.
skullUsage
Indicates how a skull is used, applied, or functionally involved in a particular context or activity.
-
E.
cranialCapacity
Indicates the volume or size of the interior space of the skull that can house the brain.
- 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_69d807629d6c8190998f1b9bb12d2ed0 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbaf8259a08190ada13c4a3078f07d |
completed | April 12, 2026, 2:43 p.m. |
| PD | Predicate disambiguation | batch_69dbae0b63748190b5e207f84b2532ea |
completed | April 12, 2026, 2:36 p.m. |
| PDg | Predicate description generation | batch_69dbaee128d88190b097be17fdd2f92b |
completed | April 12, 2026, 2:40 p.m. |
Created at: April 9, 2026, 9:43 p.m.