Triple
T23971647
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spring campaign of 1813 |
E604248
|
entity |
| Predicate | hasCoalitionMember |
P6048
|
FINISHED |
| Object | Russian Empire |
—
|
NE NERFINISHED |
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: Russian Empire | Statement: [Spring campaign of 1813, hasCoalitionMember, Russian Empire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCoalitionMember Context triple: [Spring campaign of 1813, hasCoalitionMember, Russian Empire]
-
A.
hasCoalition
Indicates that an entity participates in, belongs to, or is associated with a coalition formed with one or more other entities.
-
B.
previousCoalitionMemberOf
Indicates that an entity was formerly a member of a particular coalition but is no longer part of it.
-
C.
resultedInCoalitionIncluding
Indicates that one event, action, or circumstance led to the formation of a coalition that included a specified participant or set of participants.
-
D.
allianceMember
Indicates that an entity is a member or participant in a specific alliance or coalition.
-
E.
hasMemberParty
chosen
Indicates that a group, organization, or coalition includes a specific party as one of its members.
- 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_69e29543019c8190872462e593cc50b4 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f1d1dc3f088190a55faf6f01ddf4bf |
completed | April 29, 2026, 9:39 a.m. |
| PD | Predicate disambiguation | batch_69f161578d54819084a8b35496299993 |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 9:25 p.m.