Triple
T24271742
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Treaty of London (1518) |
E605296
|
entity |
| Predicate | involvedStateLeader |
P37571
|
FINISHED |
| Object | Henry VIII 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: Henry VIII of England | Statement: [Treaty of London (1518), involvedStateLeader, Henry VIII of England]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: involvedStateLeader Context triple: [Treaty of London (1518), involvedStateLeader, Henry VIII of England]
-
A.
hasProminentLeaderFromState
Indicates that an entity has a leading or highly influential figure whose origin or primary affiliation is with a specified state.
-
B.
involvesLeader
chosen
Indicates that the relationship or action includes or is carried out by an entity serving in a leadership role.
-
C.
designatedLeader
Indicates that one entity has been formally chosen or assigned to serve as the leader of another entity or group.
-
D.
supportedLeader
Indicates that one entity actively backed, endorsed, or provided assistance to a particular leader.
-
E.
targetLeader
Indicates that one entity is the primary leader, focal authority, or main decision-maker targeted or referenced by another entity or action.
- 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_69e2954707dc8190915551eb114cfff6 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f28d5ae9848190a622807e30319682 |
completed | April 29, 2026, 10:59 p.m. |
| PD | Predicate disambiguation | batch_69f1c450aa508190bc9d372a5f6ee47a |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 18, 2026, 12:07 a.m.