Triple
T24557771
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Treaty of Greenwich (1543) |
E607566
|
entity |
| Predicate | ratificationStatusInEngland |
P156307
|
FINISHED |
| Object | ratified |
—
|
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: ratified | Statement: [Treaty of Greenwich (1543), ratificationStatusInEngland, ratified]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ratificationStatusInEngland Context triple: [Treaty of Greenwich (1543), ratificationStatusInEngland, ratified]
-
A.
statusOfLondonAct
Indicates the legal or operational status associated with the London Act in relation to a given entity or context.
-
B.
legalStatusUnderBritish
Indicates the legal status or classification an entity holds under British law or the British legal system.
-
C.
stateOfFirstRatification
Indicates the state in which an agreement, treaty, or document was first formally ratified.
-
D.
ratifiedBy
Indicates that an agreement, treaty, or decision has been formally approved and made officially valid by a specified authority or body.
-
E.
introducedInEnglandAndWales
Indicates that something was first brought into use, implemented, or established within the jurisdiction of England and Wales.
- 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_69e2c4cae1b88190825e88d5ce8aa61e |
completed | April 17, 2026, 11:39 p.m. |
| NER | Named-entity recognition | batch_69f2a8f3fa5481909af50dca4156a22f |
completed | April 30, 2026, 12:57 a.m. |
| PD | Predicate disambiguation | batch_69f2a6b99e7c8190ba7e2dc8729a314a |
completed | April 30, 2026, 12:47 a.m. |
| PDg | Predicate description generation | batch_69f2a846c5bc81909ba50cee483bea91 |
completed | April 30, 2026, 12:54 a.m. |
Created at: April 18, 2026, 2:27 a.m.