Triple
T38110887
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Budapest Open Access Initiative |
E951650
|
entity |
| Predicate | anniversaryUpdate |
P143924
|
FINISHED |
| Object | BOAI10 |
—
|
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: BOAI10 | Statement: [Budapest Open Access Initiative, anniversaryUpdate, BOAI10]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: anniversaryUpdate Context triple: [Budapest Open Access Initiative, anniversaryUpdate, BOAI10]
-
A.
anniversaryOf
Indicates that one event or date marks the commemoration or yearly recurrence of another specific event.
-
B.
associatedWithAnniversary
chosen
Indicates a relationship where something is connected or related to an anniversary event, date, or celebration.
-
C.
anniversaryNumber
Indicates the specific ordinal count of an anniversary occurrence in a recurring commemorative event or relationship.
-
D.
completionAnniversary
Indicates the date or event marking the anniversary of when something was originally completed.
-
E.
signedOnAnniversaryOf
Indicates that an agreement or document was signed on the anniversary date of a specific prior event or reference point.
- 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_69f76f065ed08190bdfb1b6d817f5b39 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fc4748843c8190931432653be4890c |
completed | May 7, 2026, 8:03 a.m. |
| PD | Predicate disambiguation | batch_69fc45646ce481908caf292ff9f06e15 |
completed | May 7, 2026, 7:55 a.m. |
Created at: May 3, 2026, 4:21 p.m.