Triple
T33728969
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Styles Court |
E864220
|
entity |
| Predicate | notableInSeriesOrder |
P2757
|
FINISHED |
| Object | first Poirot novel setting |
—
|
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: first Poirot novel setting | Statement: [Styles Court, notableInSeriesOrder, first Poirot novel setting]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableInSeriesOrder Context triple: [Styles Court, notableInSeriesOrder, first Poirot novel setting]
-
A.
notablePerformanceSeries
Indicates a recurring set of performances or appearances by an entity that are recognized as particularly significant or noteworthy.
-
B.
notableEpisode
chosen
Indicates that a particular episode is especially significant, memorable, or noteworthy in relation to the subject.
-
C.
notableShow
Indicates that a show is especially prominent, distinguished, or significant in some noteworthy way.
-
D.
notableEP
Indicates that an entity is especially well-known or significant for a particular EP (extended play recording).
-
E.
notableEpisodeCount
Indicates the number of episodes in which the subject is notably featured or recognized.
- 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_69f3498a64cc8190b4b414c67b280d93 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a037e0953908190b2930b3c06a40129 |
completed | May 12, 2026, 7:22 p.m. |
| PD | Predicate disambiguation | batch_6a0379f6c3308190b954f7810214ceed |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:44 a.m.