Triple
T31788048
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tomb of Amenemope |
E811383
|
entity |
| Predicate | stateOfPreservationAtDiscovery |
P9592
|
FINISHED |
| Object | partially intact |
—
|
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: partially intact | Statement: [Tomb of Amenemope, stateOfPreservationAtDiscovery, partially intact]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stateOfPreservationAtDiscovery Context triple: [Tomb of Amenemope, stateOfPreservationAtDiscovery, partially intact]
-
A.
stateOfPreservation
chosen
Indicates the condition or degree to which something has been maintained, conserved, or kept intact over time.
-
B.
preservedAt
Indicates that something is kept, maintained, or conserved in a particular place or context.
-
C.
hasSubjectOfPreservation
Indicates that something is the specific focus or object being preserved or conserved within a preservation relationship.
-
D.
preservationType
Indicates the method or process by which something is preserved or kept from deterioration.
-
E.
preservedUnder
Indicates that a certain property, structure, or relation remains unchanged when a specified transformation, operation, or process is applied.
- 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_69f348e60748819082dcaa7792659803 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fd7b0503a08190ba07338365b6fcc9 |
completed | May 8, 2026, 5:56 a.m. |
| PD | Predicate disambiguation | batch_69fd7a9733dc81909199f453c0cc2bc1 |
completed | May 8, 2026, 5:54 a.m. |
Created at: April 30, 2026, 11:38 p.m.