Triple
T28408386
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aeginetan silver staters |
E719599
|
entity |
| Predicate | findspotsInclude |
P164468
|
FINISHED |
| Object | hoards across Greece |
—
|
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: hoards across Greece | Statement: [Aeginetan silver staters, findspotsInclude, hoards across Greece]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: findspotsInclude Context triple: [Aeginetan silver staters, findspotsInclude, hoards across Greece]
-
A.
locates
Indicates that one entity determines, specifies, or identifies the position or place of another entity in space or within a given context.
-
B.
placesWithin
Indicates that one place or area is located entirely inside the boundaries of another place or area.
-
C.
notableSpot
Indicates that a location is recognized as a significant or noteworthy place in some context.
-
D.
finds
Indicates that one entity discovers, locates, or comes upon another entity, often as the result of a search or encounter.
-
E.
spurLocation
Indicates the specific place or region where a spur (such as a projection, offshoot, or secondary feature) is situated relative to another entity.
- 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_69eff6f0f37c8190b37bc6fab08a9449 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f64d7329d08190bb948de084242ea6 |
completed | May 2, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_69f641e2f1708190b45b48d6a43c51d2 |
completed | May 2, 2026, 6:26 p.m. |
| PDg | Predicate description generation | batch_69f64bca8574819095e081cbb7e2f369 |
completed | May 2, 2026, 7:08 p.m. |
Created at: April 28, 2026, 1:25 a.m.