Triple
T2559469
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Georgian Armed Forces |
E57207
|
entity |
| Predicate | hasReserve |
P35319
|
FINISHED |
| Object | reserve forces |
—
|
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: reserve forces | Statement: [Georgian Armed Forces, hasReserve, reserve forces]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasReserve Context triple: [Georgian Armed Forces, hasReserve, reserve forces]
-
A.
hasReserveFunction
Indicates that an entity serves as a backup or secondary option that can perform the same function if the primary one is unavailable or fails.
-
B.
containsReservation
Indicates that one entity includes or holds a reservation associated with another entity.
-
C.
hasOnlineReservation
Indicates that an entity has a booking or reservation that was made or is managed through an online system.
-
D.
hasReserveForces
chosen
Indicates that an entity possesses additional military or security personnel kept in reserve for potential future deployment or use.
-
E.
hasReservationArea
Indicates that an entity is assigned or associated with a specific reserved area or section designated for its use.
- 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_69ab4a4ef9008190a0e6d4422b9418b7 |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abd35c6ee88190b6eaa1841d3e99a4 |
completed | March 7, 2026, 7:27 a.m. |
| PD | Predicate disambiguation | batch_69abd0caeb488190b0dd8e48d0f2777d |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:48 p.m.