Triple
T34690397
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | World Youth Day 1989 |
E890875
|
entity |
| Predicate | hasMainCelebrant |
P128792
|
FINISHED |
| Object | Pope John Paul II |
E9393
|
NE 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: Pope John Paul II | Statement: [World Youth Day 1989, hasMainCelebrant, Pope John Paul II]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMainCelebrant Context triple: [World Youth Day 1989, hasMainCelebrant, Pope John Paul II]
-
A.
hasMainCouple
Indicates that a work or narrative features a primary romantic couple who are the central focus of its relationship storyline.
-
B.
hasNotableCelebrant
chosen
Indicates that an entity (such as an event, holiday, or occasion) is associated with a specific person or group who is prominently recognized for celebrating or observing it.
-
C.
hasMainSpeaker
Indicates that one entity serves as the primary or principal speaker associated with another entity, such as an event, recording, or presentation.
-
D.
hasGroom
Indicates that an entity has a groom, i.e., is associated with a male partner in a marriage or wedding relationship.
-
E.
hasCeremonyMonth
Indicates the month during which a particular ceremony takes place or is scheduled.
- F. None of above.
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_69f349db7ab8819086808e833f472871 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a01bdacb52481909c56b0398106640e |
completed | May 11, 2026, 11:29 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a37661f7e34819086895f82d892314e |
completed | June 21, 2026, 4:18 a.m. |
| PD | Predicate disambiguation | batch_6a01bd30c8ec8190b1e54d7658b01a8d |
completed | May 11, 2026, 11:27 a.m. |
Created at: May 1, 2026, 2:05 a.m.