Triple
T8156099
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | State of Play (2003 TV serial) |
E190452
|
entity |
| Predicate | basedOnCharacterType |
P10724
|
FINISHED |
| Object | newspaper journalists |
—
|
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: newspaper journalists | Statement: [State of Play (2003 TV serial), basedOnCharacterType, newspaper journalists]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: basedOnCharacterType Context triple: [State of Play (2003 TV serial), basedOnCharacterType, newspaper journalists]
-
A.
basedOnCharacterBy
Indicates that one work, adaptation, or portrayal is derived from or inspired by a character created by another entity.
-
B.
hasTypicalCharacterType
chosen
Indicates that an entity is commonly associated with or exemplified by a particular type of character or persona.
-
C.
characterBasedOn
Indicates that one character is modeled, inspired, or derived from another real or fictional entity.
-
D.
characterSetType
Indicates the type or category of character set associated with or used by an entity.
-
E.
followsCharacterType
Indicates that one character’s behavior, role, or traits are patterned after, derived from, or constrained by a specified character type.
- 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_69ca82bfeb6481909d07b91b5cf69f59 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb44d8a37481909397b5cc321b94be |
completed | March 31, 2026, 3:51 a.m. |
| PD | Predicate disambiguation | batch_69cb36a0847c8190af9038aef78319b3 |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:37 p.m.