Triple
T3402082
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stefon |
E71677
|
entity |
| Predicate | recurringStatus |
P49091
|
FINISHED |
| Object | recurring character |
—
|
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: recurring character | Statement: [Stefon, recurringStatus, recurring character]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recurringStatus Context triple: [Stefon, recurringStatus, recurring character]
-
A.
recurringEvent
Indicates that an event occurs repeatedly over time according to some regular pattern or schedule.
-
B.
tienePeriodicidad
Indicates that something occurs, recurs, or is scheduled with a specific regular frequency or periodic pattern.
-
C.
recurrence
Indicates that an event, condition, or state happens again or repeatedly over time, often after a period of absence or resolution.
-
D.
currentStatusSince
Indicates the point in time since which an entity has held its current status or state.
-
E.
continuityStatus
Indicates the state of whether something continues without interruption or has been broken, paused, or reset over time.
- 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_69ad85aac4808190a092c9cc8911f584 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb8c96d7c8190a1f9d035996f79e3 |
completed | March 8, 2026, 5:58 p.m. |
| PD | Predicate disambiguation | batch_69adadfa73ac8190a163f93e88d217f8 |
completed | March 8, 2026, 5:12 p.m. |
| PDg | Predicate description generation | batch_69adb21a437c81908bca88d5e123d744 |
completed | March 8, 2026, 5:30 p.m. |
Created at: March 8, 2026, 3:14 p.m.