Triple
T25484756
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Weneg-Nebty |
E638672
|
entity |
| Predicate | certaintyOfReconstruction |
P158591
|
FINISHED |
| Object | low |
—
|
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: low | Statement: [Weneg-Nebty, certaintyOfReconstruction, low]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: certaintyOfReconstruction Context triple: [Weneg-Nebty, certaintyOfReconstruction, low]
-
A.
containsReconstructionOf
Indicates that one entity includes or incorporates a recreated, restored, or reconstructed version of another entity.
-
B.
reconstructedIn
Indicates that something has been rebuilt, restored, or re-created within a particular context, location, or medium.
-
C.
involvesReconstructionOf
Indicates that one entity includes, requires, or performs the rebuilding, restoration, or re-creation of another entity or its prior state.
-
D.
wasReconstructed
Indicates that something previously existing was rebuilt or restored after damage, destruction, or alteration.
-
E.
reconstructionStatus
Indicates the current state or phase of a reconstruction process that an entity is undergoing or has undergone.
- 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_69e75dbabeac8190bab30628f8b799d4 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f77ad3d0819080476fa776234cd0 |
completed | May 2, 2026, 1:09 p.m. |
| PD | Predicate disambiguation | batch_69f468421ba08190880eac99135e5970 |
completed | May 1, 2026, 8:45 a.m. |
| PDg | Predicate description generation | batch_69f46d361c348190b5fdfd805ecde01b |
completed | May 1, 2026, 9:07 a.m. |
Created at: April 21, 2026, 2:32 p.m.