Triple
T37082543
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Second Home Cemetery |
E918185
|
entity |
| Predicate | hasLanguageOfGravestoneInscriptions |
P142245
|
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: [Second Home Cemetery, hasLanguageOfGravestoneInscriptions, English]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLanguageOfGravestoneInscriptions Context triple: [Second Home Cemetery, hasLanguageOfGravestoneInscriptions, English]
-
A.
hasGravestonesWithLanguage
chosen
Indicates that a burial site contains gravestones inscribed in a specified language.
-
B.
inscriptionsLanguage
Indicates that the language used in the inscriptions on an object or surface is the specified language.
-
C.
hasLanguageOnPlaque
Indicates that a specific language appears in the text or inscription displayed on a particular plaque.
-
D.
hasGraveInscription
Indicates that an entity (typically a grave or tomb) bears a specific inscription engraved or written on it.
-
E.
secondaryLanguageOfInscriptions
Indicates that a specified language serves as the secondary language used in the inscriptions associated with a given entity.
- 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_69f76e9952b88190a6fe01ba01476520 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69ffc7b4c7f88190b6357a44e7f0940f |
completed | May 9, 2026, 11:48 p.m. |
| PD | Predicate disambiguation | batch_69ffc755f09c8190995ca00d97336988 |
completed | May 9, 2026, 11:46 p.m. |
Created at: May 3, 2026, 4:14 p.m.