Triple
T17374110
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Doctor Who: Flux |
E422388
|
entity |
| Predicate | isSerialized |
P62614
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Doctor Who: Flux, isSerialized, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isSerialized Context triple: [Doctor Who: Flux, isSerialized, true]
-
A.
isSerializable
Indicates that an object or data structure can be converted into a storable or transmittable format and later reconstructed.
-
B.
serializedIn
chosen
Indicates that something is published or presented in sequential installments within a larger medium or series.
-
C.
hasSerialization
Indicates that one entity is represented, encoded, or stored as a serialized form in another entity.
-
D.
isSerial
Indicates that an entity participates in or is characterized by a sequence of related events or items occurring one after another in order.
-
E.
serialized
Indicates that one entity has been converted into a sequential, storable or transmittable data format representing its structure or state.
- 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_69d889d6535c81908be333c01deaec4e |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e43a6b71148190bb10e1fac400d6c3 |
completed | April 19, 2026, 2:14 a.m. |
| PD | Predicate disambiguation | batch_69e3b02ac8688190a7182f1b2151d721 |
completed | April 18, 2026, 4:24 p.m. |
Created at: April 10, 2026, 5:44 a.m.