Triple
T50752
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Triple Alliance (1668) |
E995
|
entity |
| Predicate | aimedToCheck |
P860
|
FINISHED |
| Object | French 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: French expansion | Statement: [Triple Alliance (1668), aimedToCheck, French expansion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: aimedToCheck Context triple: [Triple Alliance (1668), aimedToCheck, French expansion]
-
A.
hasPrimaryGoal
Indicates that an entity’s main or most important objective is the specified goal.
-
B.
branchChecked
Indicates that a specific branch (such as in version control or a decision tree) has been examined or verified.
-
C.
target
chosen
Indicates that one entity is the intended object, goal, or focus of another entity’s action or attention.
-
D.
providedFor
Indicates that one entity supplies, furnishes, or makes something available to or on behalf of another entity for its use or benefit.
-
E.
confirmedBy
Indicates that one entity validates, approves, or verifies the truth, accuracy, or occurrence of another entity or event.
- 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_69a2480baefc81909951b14058479aa2 |
completed | Feb. 28, 2026, 1:42 a.m. |
| NER | Named-entity recognition | batch_69a24ba7016481909d595402712db6e2 |
completed | Feb. 28, 2026, 1:57 a.m. |
| PD | Predicate disambiguation | batch_69a24ac23f04819080cef9365ed990d4 |
completed | Feb. 28, 2026, 1:54 a.m. |
Created at: Feb. 28, 2026, 1:47 a.m.