Triple
T22507487
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cardinal de La Valette |
E556425
|
entity |
| Predicate | roleInThirtyYearsWar |
P108011
|
FINISHED |
| Object | led French forces in Germany |
—
|
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: led French forces in Germany | Statement: [Cardinal de La Valette, roleInThirtyYearsWar, led French forces in Germany]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInThirtyYearsWar Context triple: [Cardinal de La Valette, roleInThirtyYearsWar, led French forces in Germany]
-
A.
strategicRoleDuringWar
Indicates that an entity served a particular strategic function or importance during a specific war or armed conflict.
-
B.
roleInTimeWar
Indicates that an entity held a specific role or function during the period or events referred to as the Time War.
-
C.
roleInWarOrConflict
chosen
Indicates the specific function, position, or involvement an entity has within a particular war or conflict.
-
D.
roleDuringColdWar
Indicates the specific position, function, or involvement an entity had in the context of the Cold War period.
-
E.
reignDuringConflict
Indicates that a ruler’s period of reign overlaps in time with a specified conflict or war.
- 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_69e11e555edc81909ca803587dafd747 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15d5dec7c8190bf71ef76a2dfe9a4 |
completed | April 29, 2026, 1:22 a.m. |
| PD | Predicate disambiguation | batch_69e898be31448190be5ae7f5656f0497 |
completed | April 22, 2026, 9:45 a.m. |
Created at: April 16, 2026, 8:50 p.m.