Triple
T14759034
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elizabeth of Valois |
E346805
|
entity |
| Predicate | significantAlliance |
P600
|
FINISHED |
| Object | Franco-Spanish alliance |
—
|
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: Franco-Spanish alliance | Statement: [Elizabeth of Valois, significantAlliance, Franco-Spanish alliance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: significantAlliance Context triple: [Elizabeth of Valois, significantAlliance, Franco-Spanish alliance]
-
A.
alliance
chosen
Indicates a formal cooperative relationship between entities who agree to support each other in shared goals or interests.
-
B.
allianceDesignation
Indicates a formal relationship in which one entity designates or classifies another as an ally within an alliance.
-
C.
allianceType
Indicates the specific kind or category of alliance relationship that exists between entities.
-
D.
strengthCoalition
Indicates the degree to which a coalition is cohesive, influential, or capable of achieving its collective objectives.
-
E.
aimOfAlliance
Indicates that a specified goal, purpose, or objective is the intended focus or motivation of an alliance between 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_69d822e8896c819091169882f9b20486 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69dec7f0f5a48190af008352c26574d7 |
completed | April 14, 2026, 11:04 p.m. |
| PD | Predicate disambiguation | batch_69de8c02e5c08190943c27594026faf7 |
completed | April 14, 2026, 6:48 p.m. |
Created at: April 10, 2026, 1:30 a.m.