Triple
T30598216
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mr. Roarke |
E778840
|
entity |
| Predicate | seriesFormatElement |
P59317
|
FINISHED |
| Object | anthology-style guest stories |
—
|
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: anthology-style guest stories | Statement: [Mr. Roarke, seriesFormatElement, anthology-style guest stories]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: seriesFormatElement Context triple: [Mr. Roarke, seriesFormatElement, anthology-style guest stories]
-
A.
seriesRepresentation
Indicates that one entity is a representation, installment, or component within a larger series associated with another entity.
-
B.
seriesType
Indicates the classification or category of a series that an entity belongs to or is associated with.
-
C.
seriesDefinition
Indicates that one entity serves as the defining description or specification for a series to which another entity belongs.
-
D.
seriesWith
Indicates that one entity is part of, or grouped together in, the same series or sequence as another entity.
-
E.
usesSeriesFormat
chosen
Indicates that one entity presents or organizes its content according to the series format defined or provided by another 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_69f224a1570c8190a85d3ac330479a79 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f760a35b988190904e6267553ad2fe |
completed | May 3, 2026, 2:50 p.m. |
| PD | Predicate disambiguation | batch_69f75eb3d6f081908c933474eb359e3d |
completed | May 3, 2026, 2:41 p.m. |
Created at: April 29, 2026, 8:24 p.m.