Triple
T8953742
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kaneš |
E213419
|
entity |
| Predicate | hasArchaeologicalLevel |
P85851
|
FINISHED |
| Object | Level II |
—
|
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: Level II | Statement: [Kaneš, hasArchaeologicalLevel, Level II]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasArchaeologicalLevel Context triple: [Kaneš, hasArchaeologicalLevel, Level II]
-
A.
hasArchaeologicalLayer
Indicates that one entity contains, corresponds to, or is associated with a specific archaeological stratigraphic layer within it.
-
B.
hasArchaeologicalLayers
Indicates that one entity contains or exhibits distinct archaeological strata or layers associated with another entity (such as a site, period, or cultural phase).
-
C.
hasArchaeologicalValue
Indicates that something possesses significance or worth in the study, preservation, or interpretation of past human activity through material remains.
-
D.
hasArchaeologicalFeature
Indicates that an entity possesses, contains, or is associated with a specific archaeological feature or structure.
-
E.
hasArchaeologicalSiteType
Indicates that an entity is classified as, or associated with, a specific type or category of archaeological site.
- F. None of above. chosen
Provenance (4 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_69ca8399ad2081909f8fa41d4314c215 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc670f88d0819085d7308a5cf6c764 |
completed | April 1, 2026, 12:30 a.m. |
| PD | Predicate disambiguation | batch_69cc5ed74d288190b712d739805579dc |
completed | March 31, 2026, 11:55 p.m. |
| PDg | Predicate description generation | batch_69cc5f887108819096d45a186fc137b3 |
completed | March 31, 2026, 11:58 p.m. |
Created at: March 30, 2026, 7 p.m.