Triple
T36557605
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | the South |
E901736
|
entity |
| Predicate | militarySupportFor |
P96539
|
FINISHED |
| Object | Mordor |
—
|
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: Mordor | Statement: [the South, militarySupportFor, Mordor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: militarySupportFor Context triple: [the South, militarySupportFor, Mordor]
-
A.
militarySupportActivity
Indicates an action where one entity provides military-related assistance, resources, or operational support to another.
-
B.
militarySupportTheme
chosen
Indicates that one entity provides, requests, or is associated with military assistance, backing, or involvement in relation to another entity or situation.
-
C.
fieldOfSupport
Indicates a domain, area, or discipline in which one entity provides support, assistance, or backing to another.
-
D.
providedMilitaryAidTo
Indicates that one entity has supplied military assistance, such as weapons, training, funding, or logistical support, to another entity.
-
E.
belligerentSupport
Indicates support given to a party engaged in conflict or hostilities, often implying backing one side in a belligerent or warlike context.
- 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_69f76e634e9481908c9ba1b87ab87c26 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fd0d0ba5c48190bddb3f0e6637544c |
completed | May 7, 2026, 10:07 p.m. |
| PD | Predicate disambiguation | batch_69fd0c4324a8819086c90adf46216e0e |
completed | May 7, 2026, 10:03 p.m. |
Created at: May 3, 2026, 4:11 p.m.