Triple
T1850282
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IFI |
E41378
|
entity |
| Predicate | foundingMotivation |
P19457
|
FINISHED |
| Object | religious independence from Rome |
—
|
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: religious independence from Rome | Statement: [IFI, foundingMotivation, religious independence from Rome]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foundingMotivation Context triple: [IFI, foundingMotivation, religious independence from Rome]
-
A.
foundedAsResultOf
Indicates that one entity was established or created as a direct consequence or outcome of another event, action, or circumstance.
-
B.
describesFoundingOf
Indicates that one entity specifies or provides details about the establishment or creation (founding) of another entity.
-
C.
foundedFor
Indicates that an entity was established or created specifically to serve, support, or benefit another entity or purpose.
-
D.
motivationFor
chosen
Indicates that one entity serves as the reason, drive, or incentive behind another entity’s action, state, or occurrence.
-
E.
foundedOnOccasionOf
Indicates that something was established or created specifically in response to, or to mark, a particular event or occasion.
- 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_69a88648cd44819093303206d96d76ad |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb32d35508190bf1c487dffbecaf0 |
completed | March 7, 2026, 5:10 a.m. |
| PD | Predicate disambiguation | batch_69abafdca6d8819083c66f3a29fd9fd1 |
completed | March 7, 2026, 4:55 a.m. |
Created at: March 4, 2026, 7:33 p.m.