Triple
T16978232
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sabni |
E411869
|
entity |
| Predicate | tombFeature |
P116515
|
FINISHED |
| Object | detailed inscriptions |
—
|
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: detailed inscriptions | Statement: [Sabni, tombFeature, detailed inscriptions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tombFeature Context triple: [Sabni, tombFeature, detailed inscriptions]
-
A.
tombNotableFeature
chosen
Indicates that a tomb is distinguished or recognized for a particular notable feature or characteristic.
-
B.
burialSiteFeature
Indicates a specific physical characteristic or element associated with a burial site, such as structures, markers, or other notable features present at the place of interment.
-
C.
tombCategory
Indicates the classification or type of a tomb that an entity is associated with.
-
D.
excavatedTomb
Indicates that one entity has uncovered or dug out a tomb as part of an excavation process.
-
E.
tombDiscovered
Indicates that a tomb has been found or uncovered, typically as the result of exploration, excavation, or chance discovery.
- 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_69d886ca8f348190812768ea8d5055ce |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3d185a9408190a991bf8a1ef694f0 |
completed | April 18, 2026, 6:46 p.m. |
| PD | Predicate disambiguation | batch_69e35d4dff4881909b384e30f2d36bff |
completed | April 18, 2026, 10:30 a.m. |
Created at: April 10, 2026, 5:32 a.m.