Triple
T12636026
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Catania War Cemetery |
E301764
|
entity |
| Predicate | hasLanguageOnHeadstones |
P67509
|
FINISHED |
| Object | English |
—
|
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: English | Statement: [Catania War Cemetery, hasLanguageOnHeadstones, English]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLanguageOnHeadstones Context triple: [Catania War Cemetery, hasLanguageOnHeadstones, English]
-
A.
hasLanguageOnPlaque
chosen
Indicates that a specific language appears in the text or inscription displayed on a particular plaque.
-
B.
hasLanguageOfToponym
Indicates that a place name (toponym) is expressed in or associated with a particular language.
-
C.
hasLanguageOn
Indicates that an entity uses or is associated with a particular language in a specific context, medium, or location.
-
D.
hasLinguisticHeritage
Indicates that one entity possesses or is associated with the linguistic background, tradition, or ancestry of another entity.
-
E.
hasGraveInscription
Indicates that an entity (typically a grave or tomb) bears a specific inscription engraved or written on it.
- 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_69d7bdec9f9c8190b4bac675b7588211 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d961ae493481908f82e0d05dce20bd |
completed | April 10, 2026, 8:46 p.m. |
| PD | Predicate disambiguation | batch_69d960b47130819097e1162ed4fc993a |
completed | April 10, 2026, 8:42 p.m. |
Created at: April 9, 2026, 5:16 p.m.