Triple
T27251546
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BookTrust |
E687498
|
entity |
| Predicate | LetterboxClubFocus |
P162281
|
FINISHED |
| Object | children in care |
—
|
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: children in care | Statement: [BookTrust, LetterboxClubFocus, children in care]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: LetterboxClubFocus Context triple: [BookTrust, LetterboxClubFocus, children in care]
-
A.
fandomFocus
Indicates that one entity is primarily centered on, dedicated to, or concerned with the fan community or fan-related aspects of another entity.
-
B.
fandomScope
Indicates the extent or boundaries of a fandom-related relationship, such as how broadly or narrowly a fan’s interest, participation, or recognition applies.
-
C.
homeSeriesGenre
Indicates that a home media series (such as a TV or video series) belongs to or is categorized under a particular genre.
-
D.
fandomSharedWith
Indicates that two or more entities share interest or participation in the same fandom.
-
E.
filmSelection
Indicates the act or result of choosing a particular film from a set of available options.
- 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_69ef35567e808190a94458cd44ebff0c |
completed | April 27, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69f626b5b99081908d173630fade1f36 |
completed | May 2, 2026, 4:30 p.m. |
| PD | Predicate disambiguation | batch_69f620e38aec8190bb184edcdbd6da64 |
completed | May 2, 2026, 4:05 p.m. |
| PDg | Predicate description generation | batch_69f622a8fe7c819096e8a43db263a423 |
completed | May 2, 2026, 4:13 p.m. |
Created at: April 27, 2026, 10:45 a.m.