Triple
T33487318
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ossuary of Solferino |
E857646
|
entity |
| Predicate | containsHumanRemainsOf |
P80843
|
FINISHED |
| Object | French soldiers |
—
|
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: French soldiers | Statement: [Ossuary of Solferino, containsHumanRemainsOf, French soldiers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsHumanRemainsOf Context triple: [Ossuary of Solferino, containsHumanRemainsOf, French soldiers]
-
A.
numberOfHumanRemainsFound
Indicates the quantity of human remains that have been discovered in a given context or location.
-
B.
hasPhysicalRemains
Indicates that an entity possesses or is associated with tangible, material remains or physical evidence of its existence.
-
C.
hasBuriedRemains
chosen
Indicates that one entity contains or is the location of the buried remains of another entity.
-
D.
presentUseOfRemains
Indicates that the remains of an entity are currently being used or utilized in some manner.
-
E.
discoveredRemainsIn
Indicates that one entity found or uncovered the physical remains of another entity at a specific location.
- 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_69f3497547608190a1a0f2365fb713ee |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a0027e4a59481909417b2531daaf480 |
completed | May 10, 2026, 6:38 a.m. |
| PD | Predicate disambiguation | batch_6a0026a42bc08190ad3322ce625a523a |
completed | May 10, 2026, 6:33 a.m. |
Created at: May 1, 2026, 1:38 a.m.