Triple
T34202985
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | World Youth Day opening ceremonies |
E877435
|
entity |
| Predicate | typicallyAttendedBy |
P1509
|
FINISHED |
| Object | papal representative |
—
|
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: papal representative | Statement: [World Youth Day opening ceremonies, typicallyAttendedBy, papal representative]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicallyAttendedBy Context triple: [World Youth Day opening ceremonies, typicallyAttendedBy, papal representative]
-
A.
laterAttends
Indicates that one entity attends an event or place at a time later than another referenced attendance.
-
B.
attendanceRole
Indicates the specific capacity or role in which an entity participates in an attendance-related event or activity.
-
C.
attendanceCategory
Indicates the classification or type assigned to an entity’s attendance status within a given context or event.
-
D.
mayAttend
Indicates that an entity is permitted or eligible to be present at or participate in a particular event, activity, or gathering.
-
E.
attendedBy
chosen
Indicates that an event, place, or activity is participated in or visited by a particular person or group.
- 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_69f349aff5f0819096275315abea5344 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379f963908190846d232f386fd98f |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:55 a.m.