Triple
T35614822
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zoya the Destroya |
E1029136
|
entity |
| Predicate | hasRivalInStory |
P103334
|
FINISHED |
| Object | Liberty Belle |
—
|
NE NERFINISHED |
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: Liberty Belle | Statement: [Zoya the Destroya, hasRivalInStory, Liberty Belle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRivalInStory Context triple: [Zoya the Destroya, hasRivalInStory, Liberty Belle]
-
A.
hasPetRival
Indicates that one entity has a pet that is in a rivalry relationship with another entity's pet.
-
B.
hasRivalInFilm
Indicates that one entity serves as a rival or adversary to another within the context of a specific film.
-
C.
hasAllyInStory
Indicates that one entity is portrayed as an ally or supportive partner of another entity within the context of a specific story or narrative.
-
D.
fictionalRivalOf
chosen
Indicates a rivalry relationship that exists between two entities only within a fictional or narrative context.
-
E.
hasRivalStand
Indicates that one entity maintains a competing or opposing stand, position, or operation in relation to another entity.
- 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_69f76e0709408190bbe322bf1707ef6b |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fd231cab588190ad0953dc8f4af8f2 |
completed | May 7, 2026, 11:41 p.m. |
| PD | Predicate disambiguation | batch_69fd1aa3f1c481909fe6e9cab1383551 |
completed | May 7, 2026, 11:05 p.m. |
Created at: May 3, 2026, 4:05 p.m.