Triple
T29315858
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Avatar cycle |
E743372
|
entity |
| Predicate | continuesThrough |
P95922
|
FINISHED |
| Object | Avatar Korra |
—
|
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: Avatar Korra | Statement: [Avatar cycle, continuesThrough, Avatar Korra]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: continuesThrough Context triple: [Avatar cycle, continuesThrough, Avatar Korra]
-
A.
continuedThrough
chosen
Indicates that an event, state, or process persisted without interruption across or beyond a specified point, period, or boundary.
-
B.
continuesInto
Indicates that one entity extends forward in time, space, or sequence so that it directly proceeds into and forms a continuous progression with another entity.
-
C.
continuesFor
Indicates that an event, state, or process persists or remains in effect for a specified duration or period.
-
D.
continuesOn
Indicates that an action, process, or state persists or carries forward beyond a given point, without interruption or termination.
-
E.
continuesToward
Indicates that an entity maintains its movement or progression in the direction of a specified target or destination.
- 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_69f0912502c8819087d9e8398ee991a8 |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69f74c70fd248190a9d5543afcb08211 |
completed | May 3, 2026, 1:24 p.m. |
| PD | Predicate disambiguation | batch_69f7478e3b548190a51d5d436e2bb036 |
completed | May 3, 2026, 1:03 p.m. |
Created at: April 28, 2026, 1:19 p.m.