Triple
T12826209
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Raymond VI of Toulouse |
E306657
|
entity |
| Predicate | restoredToCommunionYear |
P28110
|
FINISHED |
| Object | 1213 |
—
|
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: 1213 | Statement: [Raymond VI of Toulouse, restoredToCommunionYear, 1213]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: restoredToCommunionYear Context triple: [Raymond VI of Toulouse, restoredToCommunionYear, 1213]
-
A.
associatedSynodYear
Indicates the specific synod year with which an entity is associated or to which it pertains.
-
B.
excommunicationYear
Indicates the year in which an entity was formally excommunicated from a religious community or institution.
-
C.
excommunicationsRemittedYear
chosen
Indicates the year in which excommunications imposed on an entity were officially lifted or remitted.
-
D.
reestablishedInYear
Indicates that an entity, previously existing and then discontinued or dissolved, was brought back into existence or operation in the specified year.
-
E.
communionSince
Indicates that a state of communion, fellowship, or shared participation between entities has been in effect continuously since a specified point in time.
- 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_69d7bdf52b94819096d6f0ba4ab50a98 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d9714208f881908f7f8a921362909a |
completed | April 10, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69d96fa08cd481909a946046ba63809f |
completed | April 10, 2026, 9:46 p.m. |
Created at: April 9, 2026, 5:33 p.m.