Triple
T26919129
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Treaty of York (1237) |
E677596
|
entity |
| Predicate | realmSignedIn |
P38750
|
FINISHED |
| Object | Kingdom of England |
—
|
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 England | Statement: [Treaty of York (1237), realmSignedIn, Kingdom of England]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: realmSignedIn Context triple: [Treaty of York (1237), realmSignedIn, Kingdom of England]
-
A.
signedInRegion
Indicates that an entity has formally signed or endorsed something within a specified geographic or jurisdictional region.
-
B.
realmTypeConnected
Indicates that two realm types are linked or associated in a way that allows interaction, transition, or shared properties between them.
-
C.
establishedByAgreementSignedIn
chosen
Indicates that something was formally created or instituted as a result of an agreement that was signed at a specific time or place.
-
D.
isSigned
Indicates that an entity has been formally endorsed or authenticated through a signature or signing action.
-
E.
roleClaimed
Indicates that an entity asserts or designates a specific role or position for itself or another entity.
- 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_69eee9bdebc48190ba90a12a63e09c73 |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f6200c30208190ae0ef84fb7afcee3 |
completed | May 2, 2026, 4:02 p.m. |
| PD | Predicate disambiguation | batch_69f611af72ac819094598dd2530d7411 |
completed | May 2, 2026, 3:01 p.m. |
Created at: April 27, 2026, 6:06 a.m.