Triple
T34105692
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Charles III, Duke of Bourbon |
E874699
|
entity |
| Predicate | propertyDisputeWith |
P26178
|
FINISHED |
| Object | Louise of Savoy |
—
|
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: Louise of Savoy | Statement: [Charles III, Duke of Bourbon, propertyDisputeWith, Louise of Savoy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: propertyDisputeWith Context triple: [Charles III, Duke of Bourbon, propertyDisputeWith, Louise of Savoy]
-
A.
property
Indicates that one entity possesses, is characterized by, or has an attribute or quality associated with another entity.
-
B.
disputeInvolves
chosen
Indicates that a particular dispute includes or concerns the specified entities as participants or parties to the conflict.
-
C.
claimedProperty
Indicates that one entity asserts ownership, possession, or a right over another entity or resource.
-
D.
houseClaim
Indicates a relationship where an entity asserts ownership, rights, or entitlement to a particular house or housing property.
-
E.
legalDisputeSubject
Indicates that a legal dispute concerns, involves, or is specifically about the referenced subject or matter.
- 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_69f349a80d4481908527317d43f5c579 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7234bcaa48190ac970759d34e254a |
completed | May 3, 2026, 10:28 a.m. |
| PD | Predicate disambiguation | batch_69f72155c48881909bd40b9aa3febd5a |
completed | May 3, 2026, 10:20 a.m. |
Created at: May 1, 2026, 1:53 a.m.