Triple
T403766
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pope |
E9339
|
entity |
| Predicate | canExercise |
P2463
|
FINISHED |
| Object | papal infallibility under specific conditions |
—
|
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 infallibility under specific conditions | Statement: [Pope, canExercise, papal infallibility under specific conditions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canExercise Context triple: [Pope, canExercise, papal infallibility under specific conditions]
-
A.
freeExerciseTest
Indicates a legal assessment of whether a law or government action improperly burdens or restricts an individual’s or group’s free exercise of religion.
-
B.
canUse
Indicates that one entity has the ability, permission, or suitability to make use of another entity or resource.
-
C.
activityLocation
Indicates the place or setting where an activity occurs or is carried out.
-
D.
canBe
chosen
Indicates that one entity has the potential, permission, or capability to become, perform as, or be classified as another entity.
-
E.
activityType
Indicates the specific kind or category of action or event that an entity is engaged in or associated with.
- 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_69a2e8004cb88190b92ed1add6abf41a |
completed | Feb. 28, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69a2eca226fc81909d6ccc38a637daa6 |
completed | Feb. 28, 2026, 1:24 p.m. |
| PD | Predicate disambiguation | batch_69a2e97066e8819083cc1b3a421b9650 |
completed | Feb. 28, 2026, 1:11 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.