Triple
T22426669
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Giant’s Graves |
E554386
|
entity |
| Predicate | foundPotteryFragments |
P19329
|
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, foundPotteryFragments, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foundPotteryFragments Context triple: [Giant’s Graves, foundPotteryFragments, yes]
-
A.
archaeologicalFindsInclude
chosen
Indicates that the set of archaeological finds at a site or context contains or encompasses the specified items or types of artifacts.
-
B.
foundInArchaeologicalZoneCategory
Indicates that an entity is located within or associated with a specific category of archaeological zone.
-
C.
discoveredRemainsIn
Indicates that one entity found or uncovered the physical remains of another entity at a specific location.
-
D.
originalFindspot
Indicates the location where an object or artifact was first discovered or found in situ.
-
E.
archaeologicalMaterialHeldIn
Indicates that an archaeological material or artifact is physically stored or curated within a specified location, such as a collection, institution, or facility.
- 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.