Triple
T24557762
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Treaty of Greenwich (1543) |
E607566
|
entity |
| Predicate | proposedGroom |
P156306
|
FINISHED |
| Object | Prince Edward 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: Prince Edward of England | Statement: [Treaty of Greenwich (1543), proposedGroom, Prince Edward of England]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: proposedGroom Context triple: [Treaty of Greenwich (1543), proposedGroom, Prince Edward of England]
-
A.
proposesMarriageAs
Indicates that one entity formally asks another entity to enter into a marital relationship.
-
B.
hasGroom
Indicates that an entity has a groom, i.e., is associated with a male partner in a marriage or wedding relationship.
-
C.
engagedTo
Indicates that two entities are formally committed to marry each other.
-
D.
bride
Indicates that an entity is a woman who is getting married or has just been married in relation to a wedding event or spouse.
-
E.
asksToMarry
Indicates that one entity proposes marriage to another, requesting that they become spouses.
- 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.