Triple
T30545413
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kiukainen |
E777399
|
entity |
| Predicate | hasArchaeologicalPeriodNamedAfterIt |
P191693
|
FINISHED |
| Object | Kiukainen culture |
—
|
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: Kiukainen culture | Statement: [Kiukainen, hasArchaeologicalPeriodNamedAfterIt, Kiukainen culture]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasArchaeologicalPeriodNamedAfterIt Context triple: [Kiukainen, hasArchaeologicalPeriodNamedAfterIt, Kiukainen culture]
-
A.
hasHeritageSiteNamedAfter
Indicates that one entity has a heritage site that is named after another entity.
-
B.
hasArchaeologicalSiteName
Indicates that an archaeological site is associated with a specific name or designation.
-
C.
hasArchaeologicalRemainsFromPeriod
Indicates that an entity contains or preserves archaeological remains originating from a specified historical period.
-
D.
ancientNameOf
Indicates that one entity is the historical or ancient name by which the other entity was formerly known.
-
E.
hasArchaeologicalSitesFrom
Indicates that an entity contains or is associated with archaeological sites dating from a specified time period or era.
- 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_69f2249d183c8190b79937c1768d2163 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fce7671f108190bf3ebf54339068b5 |
completed | May 7, 2026, 7:26 p.m. |
| PD | Predicate disambiguation | batch_69fce5b5a84c81908ac1b5b9f08d48d0 |
completed | May 7, 2026, 7:19 p.m. |
| PDg | Predicate description generation | batch_69fce76669408190b1beef8899a8a5e2 |
completed | May 7, 2026, 7:26 p.m. |
Created at: April 29, 2026, 8:19 p.m.