Triple
T10167469
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grant's Tomb |
E235241
|
entity |
| Predicate | popularRiddle |
P59665
|
FINISHED |
| Object | Who is buried in Grant's Tomb? |
—
|
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: Who is buried in Grant's Tomb? | Statement: [Grant's Tomb, popularRiddle, Who is buried in Grant's Tomb?]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: popularRiddle Context triple: [Grant's Tomb, popularRiddle, Who is buried in Grant's Tomb?]
-
A.
notableRiddle
chosen
Indicates that an entity is a well-known or significant riddle associated with another entity (such as a person, work, or context).
-
B.
puzzleType
Indicates the specific category or kind of puzzle that an item, activity, or problem belongs to.
-
C.
questionClueType
Indicates the specific type or category of clue associated with a given question.
-
D.
centralMystery
Indicates that something serves as the primary unresolved question or puzzle around which a narrative, situation, or investigation is structured.
-
E.
commonlySolvedBy
Indicates that a problem, task, or issue is typically addressed or resolved through a particular method, tool, or agent.
- 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_69ca84ceafd0819085828600e11bed6b |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdec6e016c81909ded2a16b839c405 |
completed | April 2, 2026, 4:11 a.m. |
| PD | Predicate disambiguation | batch_69cd4ba9956c8190a3e15d091e33149d |
completed | April 1, 2026, 4:45 p.m. |
Created at: March 30, 2026, 9:10 p.m.