Triple
T25187559
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | How to Rock Break-Ups and Make-Ups |
E630761
|
entity |
| Predicate | hasAdaptationRelationTo |
P43664
|
FINISHED |
| Object | How to Rock (TV series) |
E161203
|
NE 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: How to Rock (TV series) | Statement: [How to Rock Break-Ups and Make-Ups, hasAdaptationRelationTo, How to Rock (TV series)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAdaptationRelationTo Context triple: [How to Rock Break-Ups and Make-Ups, hasAdaptationRelationTo, How to Rock (TV series)]
-
A.
hasRelativeInAdaptation
Indicates that an entity has a relative (family-related counterpart) appearing in an adaptation of that entity or its source material.
-
B.
hasAdaptationRoleIn
Indicates that an entity serves a specific adaptation-related role or function within another entity, process, or context.
-
C.
hasAdaptationStrategy
Indicates that an entity employs or is associated with a specific method or approach for adapting to changing conditions or requirements.
-
D.
isAdaptation
chosen
Indicates that one work is derived from, based on, or reinterprets the content of another work.
-
E.
adaptedWithin
Indicates that one entity has been modified, adjusted, or tailored to function appropriately within the context, scope, or boundaries defined by another entity.
- F. None of above.
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_69e75a8a6d088190ba1e82a4345225e7 |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f46e0bbd2c8190a30a70dcf5523875 |
completed | May 1, 2026, 9:10 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a105d22c5f48190983eb1dca7b52b46 |
completed | May 22, 2026, 1:41 p.m. |
| PD | Predicate disambiguation | batch_69f45cfb53f4819099bba48c5057e787 |
completed | May 1, 2026, 7:57 a.m. |
Created at: April 21, 2026, 12:44 p.m.