Triple
T31929829
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saint of the Flying |
E815211
|
entity |
| Predicate | hasSubjectReligiousOrder |
P144586
|
FINISHED |
| Object | Franciscan |
—
|
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: Franciscan | Statement: [Saint of the Flying, hasSubjectReligiousOrder, Franciscan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSubjectReligiousOrder Context triple: [Saint of the Flying, hasSubjectReligiousOrder, Franciscan]
-
A.
electeeReligiousOrder
chosen
Indicates that an electee is affiliated with, or a member of, a specific religious order.
-
B.
religiousOrderSupported
Indicates that one entity provides support—such as resources, endorsement, or maintenance—to a particular religious order.
-
C.
introducedByReligiousOrder
Indicates that something (such as a practice, institution, or idea) was initiated, established, or brought into use by a religious order.
-
D.
religiousOrderBranchOf
Indicates that one religious order or congregation is an official subdivision, branch, or offshoot of another religious order.
-
E.
approvedReligiousOrder
Indicates that an authority has formally recognized and authorized a particular religious order.
- 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_69f348f3035c81908558e2339955abb3 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fed83b1d188190a318b0ad3003200a |
completed | May 9, 2026, 6:46 a.m. |
| PD | Predicate disambiguation | batch_69fed78e03548190b6e6ad93ae8d131d |
completed | May 9, 2026, 6:43 a.m. |
Created at: May 1, 2026, 12:04 a.m.