Triple
T15370010
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | sarcophagus of Senusret II (empty when found) |
E367520
|
entity |
| Predicate | foundCondition |
P115430
|
FINISHED |
| Object | empty |
—
|
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: empty | Statement: [sarcophagus of Senusret II (empty when found), foundCondition, empty]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foundCondition Context triple: [sarcophagus of Senusret II (empty when found), foundCondition, empty]
-
A.
foundWith
Indicates that one entity is discovered, observed, or obtained in the presence or company of another entity.
-
B.
foundAs
chosen
Indicates that one entity is discovered, identified, or observed in the role, form, or state represented by another entity.
-
C.
foundAfter
Indicates that one entity is discovered or located at a point in time later than another specified entity.
-
D.
foundOver
Indicates that one entity has discovered or identified another entity located above or higher than a reference point or surface.
-
E.
containsFinding
Indicates that one entity includes, encompasses, or holds a particular finding as part of its content or results.
- 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_69d85a1483788190ad93c2748e8af34b |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03e4b88a881909f9575c02aed287d |
completed | April 16, 2026, 1:41 a.m. |
| PD | Predicate disambiguation | batch_69deca9ab7e88190a9261ef27be665b1 |
completed | April 14, 2026, 11:15 p.m. |
Created at: April 10, 2026, 3:18 a.m.