Triple
T30360314
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Third Dynasty of Kish |
E772263
|
entity |
| Predicate | hasArchaeologicalVisibility |
P171329
|
FINISHED |
| Object | indirect |
—
|
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: indirect | Statement: [Third Dynasty of Kish, hasArchaeologicalVisibility, indirect]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasArchaeologicalVisibility Context triple: [Third Dynasty of Kish, hasArchaeologicalVisibility, indirect]
-
A.
archaeologicalVisibility
chosen
Indicates that something can be detected, observed, or recognized through archaeological methods or evidence.
-
B.
hasArchaeologicalFeature
Indicates that an entity possesses, contains, or is associated with a specific archaeological feature or structure.
-
C.
hasArchaeologicalValue
Indicates that something possesses significance or worth in the study, preservation, or interpretation of past human activity through material remains.
-
D.
hasArchaeologicalCertainty
Indicates that the relationship or claim is supported by archaeological evidence to a specified degree of confidence.
-
E.
hasArchaeologicalSiteStatus
Indicates that an entity holds an officially recognized status or designation as an archaeological site.
- 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_69f2248c6f5c8190a6177842bf791a3c |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fcc7338120819081cb46547d60f2cb |
completed | May 7, 2026, 5:09 p.m. |
| PD | Predicate disambiguation | batch_69fcc58566a0819082d5ea36e03bf0c6 |
completed | May 7, 2026, 5:01 p.m. |
Created at: April 29, 2026, 7:57 p.m.