Triple
T30743943
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | S.E.C.C. |
E782766
|
entity |
| Predicate | archaeologicallyIdentifiedAt |
P159904
|
FINISHED |
| Object | Cahokia |
—
|
NE NERFINISHED |
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: Cahokia | Statement: [S.E.C.C., archaeologicallyIdentifiedAt, Cahokia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: archaeologicallyIdentifiedAt Context triple: [S.E.C.C., archaeologicallyIdentifiedAt, Cahokia]
-
A.
excavatedAt
Indicates that an excavation activity took place at a specific location or site.
-
B.
archaeologicalSiteCorrespondsTo
chosen
Indicates that one archaeological site matches, aligns with, or is identified as the same as another site or reference in terms of location, features, or interpretation.
-
C.
archaeologicalIdentification
Indicates the relationship by which an entity is recognized, classified, or confirmed as an archaeological object, feature, or context based on evidence or expert analysis.
-
D.
hasArchaeologicalSiteIn
Indicates that an entity possesses, contains, or is associated with an archaeological site located within a specified place or region.
-
E.
archaeologicalSiteCode
Indicates that a specific standardized code is assigned to identify and reference 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_69f224aeb1588190897d395e8ed2acb8 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6953bafb88190a860e9c68a3dd4b2 |
completed | May 3, 2026, 12:22 a.m. |
| PD | Predicate disambiguation | batch_69f690ed5d008190831cf8e44cce28af |
completed | May 3, 2026, 12:03 a.m. |
Created at: April 29, 2026, 8:38 p.m.