Triple
T26221985
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Veronica Lodge |
E655787
|
entity |
| Predicate | rivalryReason |
P43969
|
FINISHED |
| Object | Archie Andrews romantic attention |
—
|
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: Archie Andrews romantic attention | Statement: [Veronica Lodge, rivalryReason, Archie Andrews romantic attention]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rivalryReason Context triple: [Veronica Lodge, rivalryReason, Archie Andrews romantic attention]
-
A.
rivalryBasis
chosen
Indicates the underlying reason, cause, or grounds on which a rivalry between entities is based.
-
B.
rivalryFocus
Indicates a relationship in which one entity is the primary target or center of another entity’s competitive or adversarial rivalry.
-
C.
rivalryLevel
Indicates the degree or intensity of competitive opposition or conflict between two entities.
-
D.
rivalryStatus
Indicates a competitive or adversarial relationship between entities, often involving ongoing opposition or contention.
-
E.
typeOfRivalry
Indicates a competitive or adversarial relationship between entities, specifying the particular kind or nature of rivalry that exists between them.
- 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_69ee5b4a77e08190bfcb5f8ecdc55abd |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69f621fcea1481909b6f8b3af1ee6820 |
completed | May 2, 2026, 4:10 p.m. |
| PD | Predicate disambiguation | batch_69f620debeb48190b7db395fb86cf8d9 |
completed | May 2, 2026, 4:05 p.m. |
Created at: April 26, 2026, 8:56 p.m.