Triple
T22426670
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Giant’s Graves |
E554386
|
entity |
| Predicate | foundBurntBone |
P104424
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Giant’s Graves, foundBurntBone, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foundBurntBone Context triple: [Giant’s Graves, foundBurntBone, yes]
-
A.
foundInRite
Indicates that something (such as an element, object, or action) occurs within, is used in, or is otherwise present as part of a specific rite or ritual.
-
B.
foundWith
chosen
Indicates that one entity is discovered, observed, or obtained in the presence or company of another entity.
-
C.
foundAs
Indicates that one entity is discovered, identified, or observed in the role, form, or state represented by another entity.
-
D.
foundAfter
Indicates that one entity is discovered or located at a point in time later than another specified entity.
-
E.
burdenFound
Indicates that a responsibility, obligation, or load has been identified as existing or resting upon a particular 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_69e11e4f2d0c819091aa3558ea2ee630 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15a2e438481908d43026727afa709 |
completed | April 29, 2026, 1:09 a.m. |
| PD | Predicate disambiguation | batch_69e898a327948190beee5e168006a0a7 |
completed | April 22, 2026, 9:45 a.m. |
Created at: April 16, 2026, 8:47 p.m.