Triple
T30516937
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Afrin region (historical) |
E776591
|
entity |
| Predicate | lostControlIn |
P36690
|
FINISHED |
| Object | 2018 |
—
|
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: 2018 | Statement: [Afrin region (historical), lostControlIn, 2018]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lostControlIn Context triple: [Afrin region (historical), lostControlIn, 2018]
-
A.
lostControlOfEvent
Indicates that an entity no longer has the ability to direct, manage, or influence the course or outcome of a particular event.
-
B.
lostEffectiveControlOf
chosen
Indicates that an entity no longer has practical or functional authority, influence, or command over another entity, asset, or domain, even if formal or legal control may still exist.
-
C.
lostWith
Indicates that one entity experienced a loss or defeat in conjunction with, or as part of the same side/team as, another entity.
-
D.
lostIn
Indicates that an entity has become unable to find its way or is no longer in control or possession within a particular place, situation, or context.
-
E.
lostOwnershipOf
Indicates that an entity no longer possesses or holds ownership of another entity it previously owned.
- 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_69f2249b23c4819087fa85496d92f43f |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f68a16debc8190a12f5f65ced055d7 |
completed | May 2, 2026, 11:34 p.m. |
| PD | Predicate disambiguation | batch_69f6860def1c81909d79e1f088c4b5e5 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 29, 2026, 8:16 p.m.