Triple
T28214483
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of the Blue |
E711271
|
entity |
| Predicate | rivalryBegan |
P66783
|
FINISHED |
| Object | 1895 |
—
|
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: 1895 | Statement: [Battle of the Blue, rivalryBegan, 1895]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rivalryBegan Context triple: [Battle of the Blue, rivalryBegan, 1895]
-
A.
rivalryStartPeriod
chosen
Indicates the time period or point at which a rivalry between entities begins.
-
B.
rivalryBecameProminentAfter
Indicates that a rivalry between entities became notably more intense, visible, or significant after a specified time or event.
-
C.
rivalryPeriod
Indicates the time span during which two entities are engaged in an ongoing rivalry or competitive relationship.
-
D.
hadPrimaryRivalry
Indicates that one entity was the main or most significant rival of another entity.
-
E.
rivalryNamedAfter
Indicates that a rivalry between entities is named after a particular person, place, event, or concept.
- 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_69efb51cb5288190818c1f63a266af11 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69f6562fd3488190be1acd8c526a28d2 |
completed | May 2, 2026, 7:53 p.m. |
| PD | Predicate disambiguation | batch_69f651a931748190a637e631a52bbfaa |
completed | May 2, 2026, 7:34 p.m. |
Created at: April 27, 2026, 10:41 p.m.