Triple
T38558706
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roman Church |
E925314
|
entity |
| Predicate | largestChristianChurch |
P151132
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Roman Church, largestChristianChurch, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: largestChristianChurch Context triple: [Roman Church, largestChristianChurch, true]
-
A.
isLargestChurchIn
chosen
Indicates that a church is the largest (by size, capacity, or prominence) among all churches within a specified geographic area or jurisdiction.
-
B.
wasLargestChurchIn
Indicates that a church held the status of being the largest church within a specified place or region.
-
C.
isLargestParticularChurchOf
Indicates that one church is the largest particular (sui iuris) church within a specified communion or religious body.
-
D.
wasAmongLargestChurchesIn
Indicates that a church ranked among the largest churches within a specified place or region.
-
E.
isLargestChristianDenomination
Indicates that the subject Christian denomination has the greatest number of adherents compared to all other Christian denominations in the specified context.
- 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_69f76eaeb69c8190b367df9330d6f6af |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcdfbc71c481908ba7f87907b17782 |
completed | May 7, 2026, 6:53 p.m. |
| PD | Predicate disambiguation | batch_69fcdbe580b8819087f143596b2c79c0 |
completed | May 7, 2026, 6:37 p.m. |
Created at: May 3, 2026, 4:32 p.m.