Triple
T27188325
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Treaty of Newcastle (1334) |
E683396
|
entity |
| Predicate | disadvantagedParty |
P7340
|
FINISHED |
| Object | Kingdom of Scotland |
—
|
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: Kingdom of Scotland | Statement: [Treaty of Newcastle (1334), disadvantagedParty, Kingdom of Scotland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: disadvantagedParty Context triple: [Treaty of Newcastle (1334), disadvantagedParty, Kingdom of Scotland]
-
A.
decliningParty
Indicates that an entity refuses, rejects, or turns down an offer, request, or proposal made by another entity.
-
B.
disadvantage
chosen
Indicates that one entity is in a less favorable, weaker, or hindered position relative to another in a given context.
-
C.
otherSignificantParty
Indicates that an entity has another important associated party, such as a key counterpart, partner, or involved participant in a relationship or transaction.
-
D.
negotiatingParty
Indicates that an entity is actively involved as a participant in a negotiation process with another entity.
-
E.
loserParty
Indicates that a particular political party was the one that lost in a given election or contest.
- 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_69eefad140408190b8586fdebcf9af46 |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69f625a9e3688190996e628a17d211d0 |
completed | May 2, 2026, 4:26 p.m. |
| PD | Predicate disambiguation | batch_69f620e38aec8190bb184edcdbd6da64 |
completed | May 2, 2026, 4:05 p.m. |
Created at: April 27, 2026, 9:31 a.m.