Triple
T38276437
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Camelot (2023 revival) |
E1021969
|
entity |
| Predicate | beganPreviews |
P53580
|
FINISHED |
| Object | 2023-03-09 |
—
|
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: 2023-03-09 | Statement: [Camelot (2023 revival), beganPreviews, 2023-03-09]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: beganPreviews Context triple: [Camelot (2023 revival), beganPreviews, 2023-03-09]
-
A.
previewStartDate
chosen
Indicates the date and time when a preview period for something begins.
-
B.
startedShowOn
Indicates that an entity initiated or began broadcasting or presenting a particular show on a specified platform, channel, or service.
-
C.
developerPreviewFor
Indicates a relationship where one entity serves as a developer-focused preview or early-access version of another entity.
-
D.
preparationBegan
Indicates that the initial actions or processes required for something to be carried out or occur have started.
-
E.
developmentBegan
Indicates that the process of creating or developing something was initiated at a particular time or under certain conditions.
- 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_69f76df0cddc81908d16c1556ff4097f |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fccbd826708190b5fab12c4236299a |
completed | May 7, 2026, 5:28 p.m. |
| PD | Predicate disambiguation | batch_69fcc58838e08190b8fa54aa5c165f2d |
completed | May 7, 2026, 5:02 p.m. |
Created at: May 3, 2026, 4:30 p.m.