Triple
T33283516
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Treaty of Serdica |
E852115
|
entity |
| Predicate | betweenPartyRole |
P176447
|
FINISHED |
| Object | Roman emperor |
—
|
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: Roman emperor | Statement: [Treaty of Serdica, betweenPartyRole, Roman emperor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: betweenPartyRole Context triple: [Treaty of Serdica, betweenPartyRole, Roman emperor]
-
A.
bilateralRole
Indicates a relationship where each of two entities holds a defined role with respect to the other in a mutual or two-sided interaction.
-
B.
intraPartyRole
Indicates a role or function that an entity holds within a specific political party or internal party structure.
-
C.
arePartyTo
Indicates that the entities are participants or signatories in the same agreement, contract, or legal arrangement.
-
D.
participatingParty
Indicates that an entity is involved as a participant in a particular event, activity, or transaction.
-
E.
partnerInRuleWith
Indicates that two or more entities jointly participate as partners in establishing, enforcing, or being governed by the same rule or regulatory framework.
- F. None of above. chosen
Provenance (4 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_69f349660ff48190a4568803d0b89941 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6e02ba6b881908dfafc52d3b75f1c |
completed | May 3, 2026, 5:42 a.m. |
| PD | Predicate disambiguation | batch_69f6de09c2f481909f8b2545d3208c9f |
completed | May 3, 2026, 5:32 a.m. |
| PDg | Predicate description generation | batch_69f6e029f0f88190b1f88d82a4a2cabd |
completed | May 3, 2026, 5:42 a.m. |
Created at: May 1, 2026, 1:32 a.m.