Triple
T17459818
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of the Argeș |
E425121
|
entity |
| Predicate | supportForces |
P1853
|
FINISHED |
| Object | Russian troops |
—
|
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: Russian troops | Statement: [Battle of the Argeș, supportForces, Russian troops]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportForces Context triple: [Battle of the Argeș, supportForces, Russian troops]
-
A.
supportsForce
Indicates that one entity provides the necessary structure, stability, or resistance to bear, counteract, or transmit a physical force exerted by another entity.
-
B.
supportAgainst
Indicates providing help, resources, or advocacy to oppose or resist a particular target, threat, or adversary.
-
C.
supportStructureFor
Indicates that one entity serves as a physical or functional support structure for another entity.
-
D.
supportStyle
Indicates the manner or approach by which one entity provides assistance or backing to another.
-
E.
support
chosen
Indicates that one entity provides assistance, endorsement, or backing to another entity or its actions.
- 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_69d889db0ba481908402409af3b37917 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e451444e008190944d9668d4d901fa |
completed | April 19, 2026, 3:51 a.m. |
| PD | Predicate disambiguation | batch_69e3b4f0e3fc819094e466b74622c956 |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:47 a.m.