Triple
T3306918
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sabine women |
E69472
|
entity |
| Predicate | consequenceOfAbduction |
P812
|
FINISHED |
| Object | war between Romans and Sabines |
—
|
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: war between Romans and Sabines | Statement: [Sabine women, consequenceOfAbduction, war between Romans and Sabines]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: consequenceOfAbduction Context triple: [Sabine women, consequenceOfAbduction, war between Romans and Sabines]
-
A.
abductedBy
Indicates that an entity has been forcibly taken or carried away by another entity against their will.
-
B.
abductedFrom
Indicates that an entity was forcibly taken away or kidnapped from a specified location or source.
-
C.
attemptedAbductionWithPirithous
Indicates an event where an entity participated with Pirithous in an attempt to abduct someone.
-
D.
abductionMotif
Indicates a relationship where an event, narrative, or depiction involves the motif of one entity abducting or forcibly carrying off another.
-
E.
hasConsequence
chosen
Indicates that one event, action, or condition leads to or results in another as its outcome or effect.
- 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_69ad859f218081909458d2cebbf57565 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb0caa0988190872fc7648e64571f |
completed | March 8, 2026, 5:24 p.m. |
| PD | Predicate disambiguation | batch_69ada42625308190be257f16a623a410 |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:11 p.m.