Triple
T4406735
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St Marylebone Cemetery |
E93749
|
entity |
| Predicate | hasWorldWarIIGraves |
P36715
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [St Marylebone Cemetery, hasWorldWarIIGraves, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWorldWarIIGraves Context triple: [St Marylebone Cemetery, hasWorldWarIIGraves, yes]
-
A.
sideInWorldWarII
Indicates that an entity was aligned with or participated on a particular side during World War II.
-
B.
statusDuringWorldWarII
Indicates the role, condition, or classification an entity had specifically during the period of World War II.
-
C.
worldWar
Indicates a large-scale armed conflict involving multiple nations across different regions of the world, typically encompassing numerous battles, alliances, and theaters of war.
-
D.
hasMassGraveOf
Indicates that a location or site contains a mass grave in which the referenced individuals or remains are buried.
-
E.
hasBurialsFromConflict
chosen
Indicates that the subject location or site contains burials that originated as a result of a specific conflict or violent event.
- 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_69b345158c748190a2c040fce2da9980 |
completed | March 12, 2026, 10:58 p.m. |
| NER | Named-entity recognition | batch_69b3548b1ca08190b3136867c7098d86 |
completed | March 13, 2026, 12:04 a.m. |
| PD | Predicate disambiguation | batch_69b34f5b36a881909bf2e970aa523390 |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:28 p.m.