Triple
T24322608
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Russia and Prussia |
E613008
|
entity |
| Predicate | sharedInterestIn |
P110143
|
FINISHED |
| Object | limiting French hegemony in Europe |
—
|
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: limiting French hegemony in Europe | Statement: [Russia and Prussia, sharedInterestIn, limiting French hegemony in Europe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sharedInterestIn Context triple: [Russia and Prussia, sharedInterestIn, limiting French hegemony in Europe]
-
A.
hasOverlappingInterestsFrom
Indicates that one entity shares some, but not necessarily all, interests in common with another entity, such that their sets of interests partially overlap.
-
B.
interestMayBe
Indicates that one entity potentially has an interest in, or may be interested in, another entity or subject.
-
C.
subjectInterest
Indicates that the subject has an interest in, or is concerned with, the object.
-
D.
recognizedInterest
Indicates that one entity has formally acknowledged or identified another entity’s interest in something as valid or relevant.
-
E.
shareStrategicInterestIn
chosen
Indicates that two or more entities have aligned or overlapping long-term goals or priorities regarding a particular issue, region, or domain.
- 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_69e2d7da491c8190b6e6218af50923db |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f292ad4cc881908794b501cf70b7a1 |
completed | April 29, 2026, 11:22 p.m. |
| PD | Predicate disambiguation | batch_69f1c45f45888190a9ccc225906c34bd |
completed | April 29, 2026, 8:42 a.m. |
Created at: April 18, 2026, 1:52 a.m.