Triple
T14174302
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Muscovite–Lithuanian Wars |
E351292
|
entity |
| Predicate | partlyAbout |
P380
|
FINISHED |
| Object | control of Ruthenian lands |
—
|
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: control of Ruthenian lands | Statement: [Muscovite–Lithuanian Wars, partlyAbout, control of Ruthenian lands]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partlyAbout Context triple: [Muscovite–Lithuanian Wars, partlyAbout, control of Ruthenian lands]
-
A.
partlyDefinedBy
Indicates that one entity’s nature, role, or characteristics are only partially determined or specified by another entity.
-
B.
partlyConsistsOf
Indicates that one entity is composed in part, but not entirely, of another entity.
-
C.
partlyDeclassified
Indicates that the information or document has had only some portions declassified, while other parts remain classified.
-
D.
isAbout
chosen
Indicates that one entity has as its subject, focus, or primary concern the content, topic, or theme represented by another entity.
-
E.
consideredPartOf
Indicates that one entity is regarded or treated as a component, segment, or subset of another entity within a larger whole.
- 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_69d8278834a08190b0f1784e58d7b99c |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de61b7cc3081909f4fa371e1eae130 |
completed | April 14, 2026, 3:48 p.m. |
| PD | Predicate disambiguation | batch_69de05baed64819096590e5618a3a8ed |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 10, 2026, 1:01 a.m.