Triple
T25770963
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Charles II of Anjou |
E649017
|
entity |
| Predicate | signedOrInvolvedInTreaty |
P37787
|
FINISHED |
| Object | Treaty of Anagni |
—
|
NE NERFINISHED |
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: Treaty of Anagni | Statement: [Charles II of Anjou, signedOrInvolvedInTreaty, Treaty of Anagni]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: signedOrInvolvedInTreaty Context triple: [Charles II of Anjou, signedOrInvolvedInTreaty, Treaty of Anagni]
-
A.
treatySignedWith
chosen
Indicates that a formal treaty or agreement has been officially signed between two parties.
-
B.
signedTreatyAt
Indicates that an entity formally entered into and endorsed a treaty at a specific location.
-
C.
treatySignedFor
Indicates that a formal treaty has been signed on behalf of, or in representation of, a particular entity, cause, or subject.
-
D.
roleInTreaties
Indicates the specific capacity, function, or position an entity holds within the context of one or more treaties.
-
E.
linkedToTreaty
Indicates that an entity has a formal connection or association with a specific treaty, such as being established by, governed by, or otherwise related to that treaty.
- 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_69e7ab333b508190b6d708d8d9a328ed |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f5fdf84fb88190b40280340332743e |
completed | May 2, 2026, 1:36 p.m. |
| PD | Predicate disambiguation | batch_69f5afec3e94819080d9ba86cf8c866e |
completed | May 2, 2026, 8:03 a.m. |
Created at: April 22, 2026, 5:29 a.m.