Triple
T27713883
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tomb of Richard III |
E698764
|
entity |
| Predicate | hasFloorSlab |
P164693
|
FINISHED |
| Object | inscribed ledger stone around the 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: inscribed ledger stone around the tomb | Statement: [Tomb of Richard III, hasFloorSlab, inscribed ledger stone around the tomb]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFloorSlab Context triple: [Tomb of Richard III, hasFloorSlab, inscribed ledger stone around the tomb]
-
A.
hasFloor
Indicates that one entity possesses, includes, or is associated with a particular floor or level within a structure.
-
B.
hasFloorMaterial
Indicates that an entity’s floor is made of, covered with, or constructed from a specified material.
-
C.
hasFloorFeature
Indicates that a floor possesses or includes a specific feature or characteristic.
-
D.
hasSlab
chosen
Indicates that one entity possesses, includes, or is associated with a slab component or slab-like element.
-
E.
floorBelow
Indicates that one entity is located on the floor directly beneath another entity within the same structure.
- 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_69ef590f655c81909f93893b3b3219b2 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f674e06c9481909ed0ea736408f0d7 |
completed | May 2, 2026, 10:04 p.m. |
| PD | Predicate disambiguation | batch_69f673c2f81c8190bf369226306eef09 |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 27, 2026, 3:03 p.m.