Triple
T9253102
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Etowah Indian Mounds |
E222373
|
entity |
| Predicate | containsArtifactType |
P40733
|
FINISHED |
| Object | copper plates |
—
|
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: copper plates | Statement: [Etowah Indian Mounds, containsArtifactType, copper plates]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsArtifactType Context triple: [Etowah Indian Mounds, containsArtifactType, copper plates]
-
A.
hasTypeOfArtifact
chosen
Indicates that one entity is classified as, or belongs to, a particular type or category of artifact in relation to another entity.
-
B.
hasPackageType
Indicates that an entity is associated with or classified under a particular type or category of package.
-
C.
hasArchType
Indicates that one entity possesses or is characterized by a particular architectural type or style.
-
D.
haveType
Indicates that an entity belongs to or is classified under a specified type or category.
-
E.
hasContainmentType
Indicates the specific way in which one entity is contained within or enclosed by another.
- 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_69ca841e4cd481908e738c74e958eaea |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd06b0789481908e8e44ebf1b3c713 |
completed | April 1, 2026, 11:51 a.m. |
| PD | Predicate disambiguation | batch_69cc7a4e79e48190b3200247f4624867 |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:31 p.m.