Triple
T28861179
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arch Rivalry |
E728866
|
entity |
| Predicate | rivalryRenewedIn |
P166001
|
FINISHED |
| Object | 2007 |
—
|
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: 2007 | Statement: [Arch Rivalry, rivalryRenewedIn, 2007]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rivalryRenewedIn Context triple: [Arch Rivalry, rivalryRenewedIn, 2007]
-
A.
rivalryStatus
Indicates a competitive or adversarial relationship between entities, often involving ongoing opposition or contention.
-
B.
rivalryBasis
Indicates the underlying reason, cause, or grounds on which a rivalry between entities is based.
-
C.
rivalryLevel
Indicates the degree or intensity of competitive opposition or conflict between two entities.
-
D.
rivalryPeriod
Indicates the time span during which two entities are engaged in an ongoing rivalry or competitive relationship.
-
E.
rivalryName
Indicates that a specific name or label is assigned to a rivalry relationship between two entities.
- F. None of above. chosen
Provenance (4 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_69f031a01cbc8190ba87270bb6fe4639 |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f65bb75cd08190bbdb63c093ad6210 |
completed | May 2, 2026, 8:16 p.m. |
| PD | Predicate disambiguation | batch_69f659d02f1c8190831758ac52bb54e4 |
completed | May 2, 2026, 8:08 p.m. |
| PDg | Predicate description generation | batch_69f65b136b30819090cf59fb772f35f1 |
completed | May 2, 2026, 8:14 p.m. |
Created at: April 28, 2026, 6:47 a.m.