Triple
T24661624
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Asadora morning drama series |
E610551
|
entity |
| Predicate | productionPattern |
P8034
|
FINISHED |
| Object | one main series at a time |
—
|
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: one main series at a time | Statement: [Asadora morning drama series, productionPattern, one main series at a time]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: productionPattern Context triple: [Asadora morning drama series, productionPattern, one main series at a time]
-
A.
productionCategory
Indicates the classification or type of production process, output, or activity that an entity is associated with.
-
B.
productionBlock
Indicates that one entity is prevented or restricted from producing or generating another entity.
-
C.
productionBy
Indicates that something is created, manufactured, or generated by a particular agent, organization, or process.
-
D.
pattern
chosen
Indicates that one entity exhibits, follows, or is characterized by a particular recurring form, structure, or arrangement associated with another entity.
-
E.
typicalProductionType
Indicates the usual or characteristic type of production activity associated with an 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_69e2c4d453248190a020354e93ef6282 |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f422aee0408190899efe7e24ef2b40 |
completed | May 1, 2026, 3:49 a.m. |
| PD | Predicate disambiguation | batch_69f420e92cc88190a803aecdae78a051 |
completed | May 1, 2026, 3:41 a.m. |
Created at: April 18, 2026, 2:34 a.m.