Triple
T36410880
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shakespearean histories |
E896875
|
entity |
| Predicate | focusesOnMonarch |
P184677
|
FINISHED |
| Object | King John 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: King John of England | Statement: [Shakespearean histories, focusesOnMonarch, King John of England]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: focusesOnMonarch Context triple: [Shakespearean histories, focusesOnMonarch, King John of England]
-
A.
monarchIn
Indicates that a person serves as the ruling monarch of a specified country, state, or territory.
-
B.
monarchIs
Indicates that one entity serves as the ruling monarch (such as king, queen, or equivalent sovereign) of another entity, typically a state or territory.
-
C.
monarchSubjectOf
chosen
Indicates that a monarch is the central topic or focus of a given statement, document, or informational resource.
-
D.
monarch
Indicates that an entity serves as the sovereign ruler (such as a king, queen, or emperor) over a state or territory.
-
E.
primarySupportingMonarch
Indicates that one entity serves as the main or principal supporter or ally of a monarch.
- 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_69f76e54ce408190849acc3f7758937c |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fd3d46d1f48190a1b20dd063224b7d |
completed | May 8, 2026, 1:32 a.m. |
| PD | Predicate disambiguation | batch_69fd3ae1510c81908fe1280efc17feee |
completed | May 8, 2026, 1:22 a.m. |
Created at: May 3, 2026, 4:10 p.m.