Triple
T24033811
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Black Saturday (Lebanon) |
E595172
|
entity |
| Predicate | victimIdentificationCriterion |
P107472
|
FINISHED |
| Object | religious affiliation |
—
|
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: religious affiliation | Statement: [Black Saturday (Lebanon), victimIdentificationCriterion, religious affiliation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: victimIdentificationCriterion Context triple: [Black Saturday (Lebanon), victimIdentificationCriterion, religious affiliation]
-
A.
identifiedUsing
chosen
Indicates that one entity was recognized, distinguished, or determined by means of a specified method, tool, or identifier.
-
B.
identifiedIn
Indicates that an entity is recognized, discovered, or documented within a specified source, context, or location.
-
C.
victimAlias
Indicates that an entity is known or referred to by an alternative name specifically in the role of a victim.
-
D.
victimStatus
Indicates the condition or state of a person who has been harmed or wronged as a result of an event, action, or offense.
-
E.
identified
Indicates that one entity has recognized, named, or established the identity of another entity.
- 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_69e288bf45f08190a1b6ed8cd0b9e86b |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1d8d0ec8081908f98e78944bff040 |
completed | April 29, 2026, 10:09 a.m. |
| PD | Predicate disambiguation | batch_69f1764345388190a3102b62ddb729b4 |
completed | April 29, 2026, 3:08 a.m. |
Created at: April 17, 2026, 9:56 p.m.