Triple
T35177364
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kimmerioi |
E1015745
|
entity |
| Predicate | mentionedInSourceType |
P182361
|
FINISHED |
| Object | historical sources |
—
|
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: historical sources | Statement: [Kimmerioi, mentionedInSourceType, historical sources]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mentionedInSourceType Context triple: [Kimmerioi, mentionedInSourceType, historical sources]
-
A.
mentionedWith
Indicates that two entities are mentioned together or in close association within the same context, such as a document, sentence, or conversation.
-
B.
mentionedAs
Indicates that one entity is referred to or cited by name or description in the context of another entity.
-
C.
mentionedVia
Indicates that one entity is referenced or brought up through a particular medium, channel, or mechanism represented by another entity.
-
D.
mentionedSince
Indicates that one entity has been mentioned or referred to continuously or at least once from a specified point in time onward.
-
E.
mentionsSee
Indicates that one entity explicitly refers to or cites another entity within its content.
- 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_69f76ddcc108819097f96853b7ed9ef4 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78d7802b08190bec1695d4bb2d158 |
completed | May 3, 2026, 6:01 p.m. |
| PD | Predicate disambiguation | batch_69f78b9106008190930b3b3675b737d6 |
completed | May 3, 2026, 5:53 p.m. |
| PDg | Predicate description generation | batch_69f78c337cec8190bfdab225a3cc96db |
completed | May 3, 2026, 5:56 p.m. |
Created at: May 3, 2026, 4:02 p.m.