Triple
T3306921
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sabine women |
E69472
|
entity |
| Predicate | resultOfIntervention |
P374
|
FINISHED |
| Object | truce 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: truce between Romans and Sabines | Statement: [Sabine women, resultOfIntervention, truce between Romans and Sabines]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: resultOfIntervention Context triple: [Sabine women, resultOfIntervention, truce between Romans and Sabines]
-
A.
interventionType
Indicates the specific kind or category of action, treatment, or measure applied in an intervention.
-
B.
targetOfIntervention
Indicates that an entity is the object or focus upon which an intervention, treatment, or action is directed.
-
C.
result
chosen
Indicates that one entity is produced, caused, or brought about as an outcome or consequence of another entity or process.
-
D.
intervenedIn
Indicates that an entity took action to alter, influence, or interrupt the course of an event, process, or interaction involving other entities.
-
E.
resultOfEmergency
Indicates that something occurs or exists as a direct consequence of an emergency situation or event.
- 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.