Triple
T25646744
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dan državnosti Bosne i Hercegovine |
E642984
|
entity |
| Predicate | workFreeDayIn |
P3156
|
FINISHED |
| Object | Federacija Bosne i Hercegovine |
—
|
NE NERFINISHED |
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: Federacija Bosne i Hercegovine | Statement: [Dan državnosti Bosne i Hercegovine, workFreeDayIn, Federacija Bosne i Hercegovine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workFreeDayIn Context triple: [Dan državnosti Bosne i Hercegovine, workFreeDayIn, Federacija Bosne i Hercegovine]
-
A.
restDays
Indicates the number or specific days allocated for rest or non-working periods in relation to an entity or schedule.
-
B.
workPeriod
Indicates the span of time during which an entity is engaged in a particular work or employment activity.
-
C.
isWorkHoliday
chosen
Indicates that a given day is designated as a non-working public or company holiday.
-
D.
worksOver
Indicates that one entity performs work that extends beyond or exceeds a certain limit, threshold, or standard associated with another entity.
-
E.
worksDuring
Indicates that an entity performs work or is on duty throughout a specified time period or schedule.
- 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_69e77e7ce28081908b08d65ee6e5c8be |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f5faa5765c819083c6c3bd10a3f705 |
completed | May 2, 2026, 1:22 p.m. |
| PD | Predicate disambiguation | batch_69f4807f8680819098a524158d049c63 |
completed | May 1, 2026, 10:29 a.m. |
Created at: April 21, 2026, 5:55 p.m.