Triple
T29207367
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cypro-Minoan script |
E740449
|
entity |
| Predicate | foundAtArchaeologicalSite |
P19329
|
FINISHED |
| Object | Enkomi |
—
|
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: Enkomi | Statement: [Cypro-Minoan script, foundAtArchaeologicalSite, Enkomi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foundAtArchaeologicalSite Context triple: [Cypro-Minoan script, foundAtArchaeologicalSite, Enkomi]
-
A.
foundInArchaeologicalZoneCategory
Indicates that an entity is located within or associated with a specific category of archaeological zone.
-
B.
archaeologicalFindsInclude
chosen
Indicates that the set of archaeological finds at a site or context contains or encompasses the specified items or types of artifacts.
-
C.
hasArchaeologicalSiteIn
Indicates that an entity possesses, contains, or is associated with an archaeological site located within a specified place or region.
-
D.
archaeologyAt
Indicates that an archaeological activity, study, or investigation is conducted at a specific location or site.
-
E.
discoveredByArchaeologistsIn
Indicates that something was found or uncovered by archaeologists at or within a specified place or context.
- 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_69f07cb974108190b7e86ca489a6ebb6 |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69fce28d6c3081908bf76f5db63ecf68 |
completed | May 7, 2026, 7:05 p.m. |
| PD | Predicate disambiguation | batch_69fce12d2f08819082134b5eb3db6a24 |
completed | May 7, 2026, 6:59 p.m. |
Created at: April 28, 2026, 12:09 p.m.