Triple
T33396972
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | World Meeting of Families 2015 |
E855197
|
entity |
| Predicate | papalMassLocation |
P163942
|
FINISHED |
| Object | Benjamin Franklin Parkway |
—
|
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: Benjamin Franklin Parkway | Statement: [World Meeting of Families 2015, papalMassLocation, Benjamin Franklin Parkway]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: papalMassLocation Context triple: [World Meeting of Families 2015, papalMassLocation, Benjamin Franklin Parkway]
-
A.
liturgicalLocation
chosen
Indicates the place or setting where a liturgical act, ritual, or religious service occurs.
-
B.
papacyLocatedIn
Indicates that the office or institution of the papacy is situated or based in a specific geographic or political location.
-
C.
supremePontiffResidence
Indicates the residence associated with the supreme pontiff (e.g., where the supreme pontiff officially lives or is based).
-
D.
placeOfBeatification
Indicates the location where a person was formally declared beatified in a religious context.
-
E.
locationOfConclave
Indicates the place where a conclave (a formal or secret meeting) is held or situated.
- 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_69f6f38159d08190980ad639e08f00f4 |
completed | May 3, 2026, 7:04 a.m. |
| PD | Predicate disambiguation | batch_69f6e3d7bee48190b94e0beb48a1d7fa |
completed | May 3, 2026, 5:57 a.m. |
Created at: May 1, 2026, 1:35 a.m.