Triple
T9066203
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Manbij |
E217250
|
entity |
| Predicate | ISILControlStart |
P16398
|
FINISHED |
| Object | 2014 |
—
|
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: 2014 | Statement: [Manbij, ISILControlStart, 2014]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ISILControlStart Context triple: [Manbij, ISILControlStart, 2014]
-
A.
controlStatus
Indicates that one entity has a particular level, state, or condition of control over another entity or process.
-
B.
operatesUnderControlOf
Indicates that one entity functions or carries out its activities subject to the authority, direction, or governance of another entity.
-
C.
exportControl
Indicates that an entity is subject to rules or restrictions governing the transfer or export of goods, services, or information across borders.
-
D.
controlDomain
Indicates that one entity has authority over, manages, or regulates the scope, behavior, or operations of another entity or system.
-
E.
militaryControl
chosen
Indicates that one entity exercises authoritative military power, command, or occupation over another entity or territory.
- 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_69ca83d5a7f48190b16c1e59bd43ede0 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cc94bde9c08190a4f568fbccc3c3e9 |
completed | April 1, 2026, 3:45 a.m. |
| PD | Predicate disambiguation | batch_69cc65f881248190bfd220bb28a9fb5f |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:11 p.m.