Triple
T36621228
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thuya |
E904042
|
entity |
| Predicate | discoveredInTombBy |
P137092
|
FINISHED |
| Object | James Quibell |
—
|
NE NERFINISHED |
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: James Quibell | Statement: [Thuya, discoveredInTombBy, James Quibell]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: discoveredInTombBy Context triple: [Thuya, discoveredInTombBy, James Quibell]
-
A.
foundInTomb
chosen
Indicates that an object or entity was discovered within a specific tomb or burial site.
-
B.
hasBurialChamberFor
Indicates that something (such as a structure or site) contains or is designated as a burial chamber intended for a particular individual or group.
-
C.
excavatedTomb
Indicates that one entity has uncovered or dug out a tomb as part of an excavation process.
-
D.
tombDiscovered
Indicates that a tomb has been found or uncovered, typically as the result of exploration, excavation, or chance discovery.
-
E.
containsSarcophagusOf
Indicates that one entity physically houses or encloses the sarcophagus belonging to another entity.
- 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_69f76e6ae750819096911e6e2d4d12c5 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fbc36ce1f88190a7fa1656b714e107 |
completed | May 6, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69fbbd13595c81908719f52c3d37a7e8 |
completed | May 6, 2026, 10:13 p.m. |
Created at: May 3, 2026, 4:11 p.m.