Triple
T2005421
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rose Garden burial site |
E43568
|
entity |
| Predicate | hasGravemarker |
P22905
|
FINISHED |
| Object | simple flat stone markers |
—
|
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: simple flat stone markers | Statement: [Rose Garden burial site, hasGravemarker, simple flat stone markers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGravemarker Context triple: [Rose Garden burial site, hasGravemarker, simple flat stone markers]
-
A.
hasGravestone
chosen
Indicates that one entity possesses, is associated with, or is commemorated by a gravestone.
-
B.
hasMausoleum
Indicates that one entity possesses, contains, or is associated with a mausoleum dedicated to another entity.
-
C.
hasGravesFrom
Indicates that a location or site contains graves originating from or associated with a specified source place or group.
-
D.
hasCemetery
Indicates that one entity possesses, contains, or includes a cemetery associated with it.
-
E.
hasGravestoneStyle
Indicates that an entity’s gravestone is characterized by or associated with a particular style or design.
- 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_69a88715dbbc8190b2299e29e955d997 |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abb898795481909920c1a4c4d62c2d |
completed | March 7, 2026, 5:33 a.m. |
| PD | Predicate disambiguation | batch_69abb79e63c08190982c8b44a557266f |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:37 p.m.