Triple
T2144478
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ansar al-Sharia in Libya |
E47032
|
entity |
| Predicate | activeInRegion |
P19850
|
FINISHED |
| Object | eastern 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: eastern Libya | Statement: [Ansar al-Sharia in Libya, activeInRegion, eastern Libya]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: activeInRegion Context triple: [Ansar al-Sharia in Libya, activeInRegion, eastern Libya]
-
A.
activeInTerritory
chosen
Indicates that an entity conducts operations, activities, or maintains a presence within a specified geographic territory.
-
B.
isActive
Indicates that an entity is currently functioning, engaged, or enabled within a given context or system.
-
C.
observedInRegion
Indicates that something has been detected, recorded, or seen occurring within a specified geographic or spatial region.
-
D.
statusInRegion
Indicates the specific status or condition an entity holds within a particular geographic or administrative region.
-
E.
activeInFieldFrom
Indicates that an entity is professionally or actively engaged in a particular field starting from a specified 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_69a88a1933e0819094f18426ed74180f |
completed | March 4, 2026, 7:38 p.m. |
| NER | Named-entity recognition | batch_69abbeaa14bc81908486683decd7ae42 |
completed | March 7, 2026, 5:59 a.m. |
| PD | Predicate disambiguation | batch_69abbd9846e88190b6c2941dd9ce7749 |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:44 p.m.