Triple
T35985733
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Queen |
E1040701
|
entity |
| Predicate | usedInFeudType |
P119353
|
FINISHED |
| Object | title feuds |
—
|
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: title feuds | Statement: [The Queen, usedInFeudType, title feuds]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInFeudType Context triple: [The Queen, usedInFeudType, title feuds]
-
A.
feudType
chosen
Indicates the specific kind or category of ongoing conflict or long-standing hostility that exists between entities.
-
B.
usedAgainst
Indicates that one entity is employed, applied, or deployed in opposition to, or for the purpose of affecting, another entity.
-
C.
hadFeudatory
Indicates that one entity served as a subordinate or vassal state under the authority or suzerainty of another entity.
-
D.
feud
Indicates a prolonged, mutual state of hostility or conflict between two or more parties.
-
E.
feudalType
Indicates the specific kind or category of feudal relationship, structure, or tenure that applies between the related entities.
- 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_69f76e28293c8190ae3f4e2208b87117 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fef2db323c8190821bda53f22a42be |
completed | May 9, 2026, 8:39 a.m. |
| PD | Predicate disambiguation | batch_69fef21d63c88190abf6a99b59b3c655 |
completed | May 9, 2026, 8:36 a.m. |
Created at: May 3, 2026, 4:07 p.m.