Triple
T5967716
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St. Mihiel American Cemetery |
E132793
|
entity |
| Predicate | hasNumberOfMissingCommemorated |
P41334
|
FINISHED |
| Object | 444 |
—
|
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: 444 | Statement: [St. Mihiel American Cemetery, hasNumberOfMissingCommemorated, 444]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNumberOfMissingCommemorated Context triple: [St. Mihiel American Cemetery, hasNumberOfMissingCommemorated, 444]
-
A.
numberOfMissingCommemorated
chosen
Indicates the count of commemorated entities that are missing or unaccounted for in a given context.
-
B.
missingCommemoratedNationality
Indicates that the commemorated entity’s nationality is not recorded, specified, or otherwise available.
-
C.
numberOfCommemoratedPersons
Indicates the count of distinct persons who are commemorated or honored in a given context or entity.
-
D.
hasCommemorationFunction
Indicates that something serves the role or purpose of commemorating an event, person, group, or concept.
-
E.
includesCommemoration
Indicates that one entity contains, incorporates, or features a commemoration of another entity, event, or person.
- 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_69c0086deab081908550159ca23eec9b |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c03e174c7c8190b04113f6529f5f0e |
completed | March 22, 2026, 7:08 p.m. |
| PD | Predicate disambiguation | batch_69c0335b55a48190927a5b1529edb542 |
completed | March 22, 2026, 6:22 p.m. |
Created at: March 22, 2026, 4:03 p.m.