Triple
T31965569
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Trollenberg Terror |
E816164
|
entity |
| Predicate | sourceSerialFormat |
P179837
|
FINISHED |
| Object | television serial |
—
|
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: television serial | Statement: [The Trollenberg Terror, sourceSerialFormat, television serial]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sourceSerialFormat Context triple: [The Trollenberg Terror, sourceSerialFormat, television serial]
-
A.
serializationFormatFor
Indicates the data serialization format used to encode or represent a given resource or entity.
-
B.
serialModeDescription
Indicates the description or textual explanation of a device’s serial communication mode or configuration.
-
C.
serialInterface
Indicates a relationship where data is transmitted between components over a serial communication interface (one bit at a time over a communication line or bus).
-
D.
originalSerialization
Indicates that one entity is the initial or source serialized form from which another serialized representation is derived.
-
E.
serialNumber
Indicates a unique identifying code assigned to an individual item or instance within a series or batch.
- F. None of above. chosen
Provenance (4 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_69f348f5ae5481909da0247869f51955 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f727afd5d88190ad48735cd1b32787 |
completed | May 3, 2026, 10:47 a.m. |
| PD | Predicate disambiguation | batch_69f72737c42c8190a3f781a5e98868ff |
completed | May 3, 2026, 10:45 a.m. |
| PDg | Predicate description generation | batch_69f727ad9ff88190ba8069dd48b2e98f |
completed | May 3, 2026, 10:47 a.m. |
Created at: May 1, 2026, 12:09 a.m.