Triple
T5436043
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pawukon |
E122009
|
entity |
| Predicate | repeatsAfter |
P24840
|
FINISHED |
| Object | 210 days |
—
|
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: 210 days | Statement: [Pawukon, repeatsAfter, 210 days]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: repeatsAfter Context triple: [Pawukon, repeatsAfter, 210 days]
-
A.
repetitionOf
Indicates that one entity is a repeated occurrence or instance of another entity, preserving the same content or pattern.
-
B.
usesRepetition
Indicates that one entity employs repeated elements, actions, or patterns as a deliberate feature or technique in relation to another entity or context.
-
C.
notableRepeatBy
Indicates that an action, event, or pattern occurs repeatedly and is notably performed, exhibited, or instantiated by a particular entity.
-
D.
causesRepetitionOf
Indicates that one entity brings about or is responsible for the recurrence or repeated occurrence of another entity or event.
-
E.
repetitionPattern
chosen
Indicates a recurring structure or sequence in which an action, event, or element is repeated over time or across instances.
- 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_69bd46400768819092925d461c0b8432 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd922f66bc8190b7d47fd68d2fcf2e |
completed | March 20, 2026, 6:30 p.m. |
| PD | Predicate disambiguation | batch_69bd919aeb048190b786f814177d6cd9 |
completed | March 20, 2026, 6:27 p.m. |
Created at: March 20, 2026, 2:06 p.m.