Triple
T9803202
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Government of National Salvation (Tripoli-based) |
E237890
|
entity |
| Predicate | regionOfControl |
P82949
|
FINISHED |
| Object | western Libya |
—
|
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: western Libya | Statement: [Government of National Salvation (Tripoli-based), regionOfControl, western Libya]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regionOfControl Context triple: [Government of National Salvation (Tripoli-based), regionOfControl, western Libya]
-
A.
controlsRegion
chosen
Indicates that one entity has authoritative power or governing influence over a specified geographic or administrative region.
-
B.
rangeControlledBy
Indicates that the extent or scope of something is regulated, limited, or determined by another entity.
-
C.
regionRuled
Indicates that a particular region is governed or controlled by a specified ruler or authority.
-
D.
occupiedRegion
Indicates that an entity has taken control of and is currently holding a specific geographic area or region.
-
E.
coreRegionOf
Indicates that one entity constitutes the central or most essential part of another entity’s structure, area, or domain.
- 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_69ca84dd4608819097ff4ed00feca280 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdab78832481909b184b21a8a46e50 |
completed | April 1, 2026, 11:34 p.m. |
| PD | Predicate disambiguation | batch_69cd03dd2da881909052fbf29736a773 |
completed | April 1, 2026, 11:39 a.m. |
Created at: March 30, 2026, 8:29 p.m.