Triple
T26973102
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NEWBORN |
E679372
|
entity |
| Predicate | unveiledOnSameDayAs |
P161402
|
FINISHED |
| Object | Kosovo declaration of independence |
—
|
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: Kosovo declaration of independence | Statement: [NEWBORN, unveiledOnSameDayAs, Kosovo declaration of independence]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: unveiledOnSameDayAs Context triple: [NEWBORN, unveiledOnSameDayAs, Kosovo declaration of independence]
-
A.
unveiledOn
Indicates the date or event at which something (such as a product, artwork, or plan) was formally revealed or made public.
-
B.
unveiledBy
Indicates that something (such as an object, artwork, or project) was formally revealed or presented to the public by a particular agent or entity.
-
C.
reunveiledOn
Indicates that something was revealed or made publicly known again on a specific date or occasion.
-
D.
unveiledAs
Indicates that one entity is revealed, presented, or disclosed in the role, identity, or form of another entity.
-
E.
unveiledInYear
Indicates the specific calendar year in which something was formally revealed or made publicly known.
- 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_69eeeb507a7081909d516e1fa08b7d29 |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f6212682488190bcf8ff6a98296bdf |
completed | May 2, 2026, 4:07 p.m. |
| PD | Predicate disambiguation | batch_69f611af72ac819094598dd2530d7411 |
completed | May 2, 2026, 3:01 p.m. |
| PDg | Predicate description generation | batch_69f6125e54e0819088ee33a20efcc9e6 |
completed | May 2, 2026, 3:03 p.m. |
Created at: April 27, 2026, 6:40 a.m.