Triple
T8432151
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Neša |
E199137
|
entity |
| Predicate | inferredLocation |
P28981
|
FINISHED |
| Object | near modern Kayseri |
—
|
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: near modern Kayseri | Statement: [Neša, inferredLocation, near modern Kayseri]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inferredLocation Context triple: [Neša, inferredLocation, near modern Kayseri]
-
A.
introducedFromLocation
Indicates that something or someone was brought, initiated, or first made present starting from a specified location.
-
B.
refersToLocation
Indicates that one entity designates, points to, or identifies a specific location associated with it.
-
C.
deltaLocation
Indicates a change or difference between two locations, typically specifying how one location has shifted relative to another.
-
D.
apseLocation
Indicates the specific place or position where an apse is situated within a larger structure or context.
-
E.
possibleLocation
chosen
Indicates that an entity may be located at, or could plausibly occur in, a specified place or spatial 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_69ca8313c99081909a5c6d83b91de5b3 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe30fba4081908bfdef3faf5baceb |
completed | March 31, 2026, 3:06 p.m. |
| PD | Predicate disambiguation | batch_69cbd0ec200c8190b0299e2b0b4bdcc2 |
completed | March 31, 2026, 1:49 p.m. |
Created at: March 30, 2026, 6:07 p.m.