Triple
T27856600
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | British Ambassador to Saxony |
E704104
|
entity |
| Predicate | postedTo |
P164354
|
FINISHED |
| Object | court of the Elector of Saxony |
—
|
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: court of the Elector of Saxony | Statement: [British Ambassador to Saxony, postedTo, court of the Elector of Saxony]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: postedTo Context triple: [British Ambassador to Saxony, postedTo, court of the Elector of Saxony]
-
A.
postedIn
Indicates that a piece of content or message was submitted or shared within a particular forum, group, channel, or location.
-
B.
laterPosting
Indicates that one posting, message, or publication occurs at a later time than another in a temporal sequence.
-
C.
postPosition
Indicates that one entity is located behind or to the rear of another entity in space or sequence.
-
D.
isPostOf
Indicates that one entity is a post (e.g., a message or publication) that belongs to, was created for, or is associated with another entity (such as a user, thread, or topic).
-
E.
isPostedBy
Indicates that a piece of content (such as a message, post, or item) was created and published by a particular user or source.
- 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_69ef840e614c8190a88cf9638c14a265 |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f644de4a84819087ddb84757fc4585 |
completed | May 2, 2026, 6:39 p.m. |
| PD | Predicate disambiguation | batch_69f641def1e88190a05bf865ced78b23 |
completed | May 2, 2026, 6:26 p.m. |
| PDg | Predicate description generation | batch_69f643e818d481908fc66bc91bd25d77 |
completed | May 2, 2026, 6:35 p.m. |
Created at: April 27, 2026, 6:14 p.m.