Triple
T23725805
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Merit |
E586270
|
entity |
| Predicate | tombCondition |
P153720
|
FINISHED |
| Object | well-preserved |
—
|
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: well-preserved | Statement: [Merit, tombCondition, well-preserved]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tombCondition Context triple: [Merit, tombCondition, well-preserved]
-
A.
tombCategory
Indicates the classification or type of a tomb that an entity is associated with.
-
B.
tombDiscovered
Indicates that a tomb has been found or uncovered, typically as the result of exploration, excavation, or chance discovery.
-
C.
hasTombs
Indicates that one entity possesses, contains, or is the location of one or more tombs associated with another entity.
-
D.
tombNumber
Indicates the specific identifying number assigned to a particular tomb within a set of tombs.
-
E.
tombOwnership
Indicates a relationship in which one entity holds legal or traditional ownership rights over a specific tomb.
- F. None of above. chosen
Provenance (4 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_69e24906fb108190a6898751e46bdc11 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b915a888819088e92f99711e8120 |
completed | April 29, 2026, 7:53 a.m. |
| PD | Predicate disambiguation | batch_69f155e4b1148190836ede4741dcb888 |
completed | April 29, 2026, 12:50 a.m. |
| PDg | Predicate description generation | batch_69f15b453da88190889a8d9b21727958 |
completed | April 29, 2026, 1:13 a.m. |
Created at: April 17, 2026, 7:08 p.m.