Triple
T25725157
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reign of Charles IX of France |
E645097
|
entity |
| Predicate | keyNobleFaction |
P25962
|
FINISHED |
| Object | House of Guise |
—
|
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: House of Guise | Statement: [Reign of Charles IX of France, keyNobleFaction, House of Guise]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: keyNobleFaction Context triple: [Reign of Charles IX of France, keyNobleFaction, House of Guise]
-
A.
notableNobleFaction
chosen
Indicates that a noble is significantly associated with or belongs to a particularly prominent or influential noble faction.
-
B.
keyFortress
Indicates that one entity functions as a key or means of access, control, or unlocking for a particular fortress or strongly secured place represented by the other entity.
-
C.
keyCoalition
Indicates a coalition relationship where an entity plays a central or decisive role within that coalition.
-
D.
namedForAllegiance
Indicates that an entity is named in reference to, or in honor of, a particular allegiance, affiliation, or loyalty.
-
E.
factionName
Indicates the specific name assigned to a faction with which an entity is associated.
- 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_69e77e8476fc8190bd5e9d05b89fad0a |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f5fcb6562481909de5461493ab10b1 |
completed | May 2, 2026, 1:31 p.m. |
| PD | Predicate disambiguation | batch_69f480824a1c81908a8a492eedbc2596 |
completed | May 1, 2026, 10:29 a.m. |
Created at: April 21, 2026, 10:17 p.m.