Triple
T19788176
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Žepa |
E475332
|
entity |
| Predicate | UNSafeAreaResolutionDate |
P137333
|
FINISHED |
| Object | 6 May 1993 |
—
|
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: 6 May 1993 | Statement: [Žepa, UNSafeAreaResolutionDate, 6 May 1993]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: UNSafeAreaResolutionDate Context triple: [Žepa, UNSafeAreaResolutionDate, 6 May 1993]
-
A.
rescueDate
Indicates the date on which a rescue action or operation took place.
-
B.
unRecognitionDate
Indicates the date on which a previously recognized status, entity, or relationship is officially withdrawn or no longer acknowledged.
-
C.
surrenderDate
Indicates the date on which an entity formally yields control, possession, or rights, typically ending its claim or resistance.
-
D.
dateReRaised
Indicates that a previously raised issue, request, or event has been brought up again on a later date.
-
E.
reentryDate
Indicates the date on which an entity returns or is admitted again after a prior departure, exit, or release.
- F. None of above. chosen
Provenance (4 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_69d8e51b014081908b263e167370529a |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e65389c9ac81909e61b3cbb9213e72 |
completed | April 20, 2026, 4:25 p.m. |
| PD | Predicate disambiguation | batch_69e53053ed2881908400becdfada7fd3 |
completed | April 19, 2026, 7:43 p.m. |
| PDg | Predicate description generation | batch_69e532bcf41c8190b685b5adf46a60fc |
completed | April 19, 2026, 7:53 p.m. |
Created at: April 10, 2026, 1:49 p.m.