Triple
T9066433
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kurdish Hezbollah (Turkey) |
E217255
|
entity |
| Predicate | becameActive |
P7730
|
FINISHED |
| Object | 1980s |
—
|
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: 1980s | Statement: [Kurdish Hezbollah (Turkey), becameActive, 1980s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: becameActive Context triple: [Kurdish Hezbollah (Turkey), becameActive, 1980s]
-
A.
activatedFor
Indicates that something has been enabled, triggered, or made operational specifically on behalf of or in the context of a particular entity or target.
-
B.
activeFrom
chosen
Indicates the starting point in time from which an entity or relationship is considered active or in effect.
-
C.
reactivatedDuring
Indicates that an entity becomes active again within the time span or context defined by another event or condition.
-
D.
isActive
Indicates that an entity is currently functioning, engaged, or enabled within a given context or system.
-
E.
activeInState
Indicates that an entity is currently functioning, operating, or valid within a specified state or condition.
- 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.