Triple
T4815773
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Khertvisi Fortress |
E107583
|
entity |
| Predicate | dateOfFirstFortification |
P28167
|
FINISHED |
| Object | at least 2nd century BC |
—
|
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: at least 2nd century BC | Statement: [Khertvisi Fortress, dateOfFirstFortification, at least 2nd century BC]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dateOfFirstFortification Context triple: [Khertvisi Fortress, dateOfFirstFortification, at least 2nd century BC]
-
A.
earliestRecordedFortification
chosen
Indicates that the subject is the earliest known or first historically recorded example of a particular fortification associated with the object.
-
B.
constructionBeganAsFortressIn
Indicates that the construction of something originally began with the purpose or function of serving as a fortress at a specified time or in a specified place.
-
C.
wasFortifiedBy
Indicates that a place or structure received defensive strengthening or fortification through the actions or resources of a specified agent or entity.
-
D.
originalCastleFoundedIn
Indicates the specific year or time period when the original version of a castle was first established or built.
-
E.
siegeStartDate
Indicates the calendar date on which a siege begins.
- 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_69bd43f9efa081908314cb3e94fa1695 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6ddd17d881909f7731ff2b460e83 |
completed | March 20, 2026, 3:55 p.m. |
| PD | Predicate disambiguation | batch_69bd6c1dfa3481909d240d50ed0ee38c |
completed | March 20, 2026, 3:47 p.m. |
Created at: March 20, 2026, 1:23 p.m.