Triple
T5939778
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lord of Balaguer |
E132137
|
entity |
| Predicate | usedInMonarchicProtocol |
P17686
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Lord of Balaguer, usedInMonarchicProtocol, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInMonarchicProtocol Context triple: [Lord of Balaguer, usedInMonarchicProtocol, yes]
-
A.
usedInMonarchy
chosen
Indicates that something is employed, practiced, or functions within the context of a monarchical system of government.
-
B.
appliedToMonarch
Indicates that an action, policy, or attribute is directed toward or exercised upon a monarch.
-
C.
monarchIn
Indicates that a person serves as the ruling monarch of a specified country, state, or territory.
-
D.
associatedWithMonarch
Indicates a relationship where an entity has a connection or affiliation with a monarch, such as through service, governance, lineage, or formal association.
-
E.
monarchicContext
Indicates that the relationship or action occurs within, is shaped by, or pertains to a monarchical system of rule or authority.
- 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_69c0085c55dc8190aa90e242c956e2fa |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c03f26f51881908cc253fe5775a1fc |
completed | March 22, 2026, 7:12 p.m. |
| PD | Predicate disambiguation | batch_69c03355caf08190b960563a1aed23f9 |
completed | March 22, 2026, 6:22 p.m. |
Created at: March 22, 2026, 4:01 p.m.