Triple
T10882305
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Georgian–Ossetian conflict |
E256951
|
entity |
| Predicate | ongoingAsOf |
P28838
|
FINISHED |
| Object | 21st century |
—
|
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: 21st century | Statement: [Georgian–Ossetian conflict, ongoingAsOf, 21st century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ongoingAsOf Context triple: [Georgian–Ossetian conflict, ongoingAsOf, 21st century]
-
A.
isOngoing
chosen
Indicates that an action, process, or state is currently in progress and has not yet been completed or concluded.
-
B.
hasOngoing
Indicates that one entity is currently engaged in, experiencing, or maintaining an activity, state, or process that has not yet concluded.
-
C.
wasOngoingProjectUntil
Indicates that an activity or project was in progress and continued up to a specified end time or event.
-
D.
actualStatus
Indicates the current, real-world state or condition of an entity, as opposed to a planned, expected, or nominal status.
-
E.
goesOn
Indicates that one entity participates in, boards, or travels using another entity, such as a vehicle, trip, or event.
- 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_69d6aa848804819081b2713ca0bedf06 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d751da559c819094c3680a9f734ee7 |
completed | April 9, 2026, 7:14 a.m. |
| PD | Predicate disambiguation | batch_69d70d360c388190a3d829fe8862434f |
completed | April 9, 2026, 2:21 a.m. |
Created at: April 8, 2026, 9:21 p.m.