Triple
T38139289
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sign of the Times |
E952433
|
entity |
| Predicate | isSoloWorkBeyond |
P190139
|
FINISHED |
| Object | One Direction |
E128211
|
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: One Direction | Statement: [Sign of the Times, isSoloWorkBeyond, One Direction]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isSoloWorkBeyond Context triple: [Sign of the Times, isSoloWorkBeyond, One Direction]
-
A.
isStandaloneWork
Indicates that a work exists independently and is not part of a larger series, collection, or multi-part work.
-
B.
isSoloPartFor
Indicates that something functions as an individual or standalone component within a larger whole or composition.
-
C.
otherWork
Indicates that one work is related to another work by the same creator, but is distinct from the primary or referenced work.
-
D.
worksIndependentlyOf
Indicates that one entity performs its function or activity without relying on, being influenced by, or requiring coordination with another entity.
-
E.
isWork
Indicates that an entity functions as a work (such as a creation, product, or task) in relation to another entity.
- F. None of above. chosen
Provenance (5 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_69f76f09a7148190a4b91c0bacdc127a |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fcb089a8f881909aa9e722babd43f7 |
completed | May 7, 2026, 3:32 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a417128a22c8190899478a4cc0f07f1 |
completed | June 28, 2026, 7:08 p.m. |
| PD | Predicate disambiguation | batch_69fc45666c5c8190913bd632ac0e5b84 |
completed | May 7, 2026, 7:55 a.m. |
| PDg | Predicate description generation | batch_69fcb088aac481909db90804faff315f |
completed | May 7, 2026, 3:32 p.m. |
Created at: May 3, 2026, 4:21 p.m.