Triple
T33396985
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | World Meeting of Families 2015 |
E855197
|
entity |
| Predicate | typeOfGathering |
P115172
|
FINISHED |
| Object | ecclesial gathering |
—
|
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: ecclesial gathering | Statement: [World Meeting of Families 2015, typeOfGathering, ecclesial gathering]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfGathering Context triple: [World Meeting of Families 2015, typeOfGathering, ecclesial gathering]
-
A.
typeOfEvent
Indicates that one entity is classified as a specific kind or category of event.
-
B.
partyCategory
Indicates the classification or type assigned to a party within a given context or system.
-
C.
gathering
chosen
Indicates that one or more entities are coming together or being brought together into a group at a particular time or place.
-
D.
typicalParty
Indicates that an entity is a usual, standard, or characteristic participant in a given type of event, situation, or relationship.
-
E.
organisedEvent
Indicates that an entity planned, coordinated, and carried out an event.
- 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_69f3496e3f1c8190bcecfa82aa9d17ff |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a00b03a50a88190bfb95cdcfc6142a2 |
completed | May 10, 2026, 4:20 p.m. |
| PD | Predicate disambiguation | batch_6a00afe55f248190b2cb4c7e62cc3ffc |
completed | May 10, 2026, 4:18 p.m. |
Created at: May 1, 2026, 1:35 a.m.