Triple
T3436414
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South Eastern Reporter |
E72462
|
entity |
| Predicate | belongsToSeriesType |
P14858
|
FINISHED |
| Object | regional reporter |
—
|
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: regional reporter | Statement: [South Eastern Reporter, belongsToSeriesType, regional reporter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: belongsToSeriesType Context triple: [South Eastern Reporter, belongsToSeriesType, regional reporter]
-
A.
isSeriesOf
Indicates that one entity is a sequence or set of related items that collectively form a series associated with another entity.
-
B.
connectsToSeries
Indicates that one entity is linked or associated with a particular series, establishing a connection or membership relationship between them.
-
C.
intendedForSeries
Indicates that something is designed, created, or designated to be used within or as part of a particular series.
-
D.
associatedWithEpisodeType
Indicates that something has a connection or linkage to a particular type or category of episode.
-
E.
seriesType
chosen
Indicates the classification or category of a series that an entity belongs to or is associated with.
- 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_69ad85af50288190a854b76653deee6f |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb9f2e4b4819085336fb539daf3c7 |
completed | March 8, 2026, 6:03 p.m. |
| PD | Predicate disambiguation | batch_69adae00ad588190bef24373b58a2e1a |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:16 p.m.