Triple
T30896161
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bab al-Azizia compound, Tripoli |
E787026
|
entity |
| Predicate | controlledByUntil |
P25341
|
FINISHED |
| Object | 2011 |
—
|
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: 2011 | Statement: [Bab al-Azizia compound, Tripoli, controlledByUntil, 2011]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: controlledByUntil Context triple: [Bab al-Azizia compound, Tripoli, controlledByUntil, 2011]
-
A.
controlledByAtEnd
Indicates that one entity has control or governing authority over another entity at the final point or conclusion of a specified process, period, or event.
-
B.
governsUntil
chosen
Indicates that one entity exercises governing authority or control over another entity up to, but not beyond, a specified time or condition.
-
C.
controlledSince
Indicates that one entity has held control or authority over another entity starting from a specified point in time.
-
D.
controlledAfter
Indicates that one entity gains or maintains control over another entity only after a specified time, event, or condition has occurred.
-
E.
managedUntil
Indicates that one entity was responsible for managing or overseeing another entity up to a specific point in time.
- 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_69f224bcbcb48190836df847424e4057 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fd7b0503a08190ba07338365b6fcc9 |
completed | May 8, 2026, 5:56 a.m. |
| PD | Predicate disambiguation | batch_69fd7a9733dc81909199f453c0cc2bc1 |
completed | May 8, 2026, 5:54 a.m. |
Created at: April 29, 2026, 8:49 p.m.