Triple
T5334650
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Plombières Agreement |
E123796
|
entity |
| Predicate | politicalObjectiveOfFrance |
P15014
|
FINISHED |
| Object | territorial expansion |
—
|
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: territorial expansion | Statement: [Plombières Agreement, politicalObjectiveOfFrance, territorial expansion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: politicalObjectiveOfFrance Context triple: [Plombières Agreement, politicalObjectiveOfFrance, territorial expansion]
-
A.
objectiveOfFrance
chosen
Indicates that something is an objective, goal, or aim pursued by France.
-
B.
royalistObjective
Indicates that an entity’s goal, purpose, or intended outcome is to support, preserve, or advance a monarchy or royal authority.
-
C.
FrenchObjective
Indicates that an entity serves as the goal, target, or object of an action or relation specifically within a French linguistic or contextual framework.
-
D.
obligationsOfFrance
Indicates that the specified obligations are those that France is responsible for or bound to fulfill.
-
E.
significanceForFrance
Indicates that something holds particular importance, impact, or relevance specifically in the context of France.
- 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_69bd464b07f8819095aa76577c9829e4 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd85ae52c08190968a5567b7e6b794 |
completed | March 20, 2026, 5:36 p.m. |
| PD | Predicate disambiguation | batch_69bd84583dbc819088a03e3afb30178c |
completed | March 20, 2026, 5:31 p.m. |
Created at: March 20, 2026, 2 p.m.