Triple
T37228676
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SEPP International S.A. |
E923071
|
entity |
| Predicate | hasWorkFormat |
P58459
|
FINISHED |
| Object | episodic series |
—
|
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: episodic series | Statement: [SEPP International S.A., hasWorkFormat, episodic series]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWorkFormat Context triple: [SEPP International S.A., hasWorkFormat, episodic series]
-
A.
hasWorkingFormat
Indicates that one entity possesses or is associated with a functional or operational format of another entity.
-
B.
hasWorkForm
chosen
Indicates that an entity is associated with a particular form, format, or mode in which its work or activity is carried out or expressed.
-
C.
basedInWorkFormat
Indicates that an entity operates or is situated within a particular work format (such as remote, hybrid, or on-site) as its primary mode of working.
-
D.
hasProductionFormat
Indicates that an entity is associated with, or presented in, a particular production or media format.
-
E.
hasWorkPart
Indicates that one work is a component, section, or constituent part of another, larger work.
- 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_69f76ea7f0008190b31b8e30f3d05a71 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fed357b2b4819084c709056a54461f |
completed | May 9, 2026, 6:25 a.m. |
| PD | Predicate disambiguation | batch_69fed103d9cc81909b11619745110c61 |
completed | May 9, 2026, 6:15 a.m. |
Created at: May 3, 2026, 4:15 p.m.