Triple
T1555932
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Edward V of England |
E33203
|
entity |
| Predicate | legalStatusAfter1483 |
P28623
|
FINISHED |
| Object | declared illegitimate |
—
|
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: declared illegitimate | Statement: [Edward V of England, legalStatusAfter1483, declared illegitimate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legalStatusAfter1483 Context triple: [Edward V of England, legalStatusAfter1483, declared illegitimate]
-
A.
legalStatusAfter1792
Indicates the legal status or condition that an entity held after the year 1792.
-
B.
legalStatusModern
Indicates the current legal standing or classification of an entity under contemporary law or regulatory frameworks.
-
C.
legalStatusClarifiedBy
Indicates that the legal status of something is defined, explained, or resolved by a specific document, decision, or authoritative act.
-
D.
historicalStatusOf
chosen
Indicates the historical condition, role, or classification that an entity held during a specific past period or context.
-
E.
legalHistory
Indicates that there exists a record of past legal actions, cases, or statuses associated with an 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_69a885ef9cf48190b0af0f5ce3d02231 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a9407d9d1481909597af97b16512cc |
completed | March 5, 2026, 8:36 a.m. |
| PD | Predicate disambiguation | batch_69a907b688d081908171f89010c53973 |
completed | March 5, 2026, 4:33 a.m. |
Created at: March 4, 2026, 7:27 p.m.