Triple
T1197303
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aim High |
E25696
|
entity |
| Predicate | hasStudioRecording |
P9348
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Aim High, hasStudioRecording, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStudioRecording Context triple: [Aim High, hasStudioRecording, yes]
-
A.
hasNotableRecordingBy
Indicates that an entity (such as a work or composition) has a well-known or significant recording created or performed by a specified agent (such as an artist, ensemble, or label).
-
B.
recordedFor
Indicates that something has been documented, captured, or logged on behalf of or in association with a particular entity or context.
-
C.
recorded
chosen
Indicates that one entity captured, stored, or documented information, audio, video, or data about another entity or event.
-
D.
recordedWith
Indicates that something was captured, documented, or produced using a particular tool, device, medium, or method.
-
E.
hasMainStudioShow
Indicates that an entity serves as the primary studio-based show associated with another entity (such as a network, channel, or program brand).
- 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_69a49429f5ec8190a6a205eb0ae81e5e |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4bd9a305c819091513394f1b67784 |
completed | March 1, 2026, 10:28 p.m. |
| PD | Predicate disambiguation | batch_69a4bb5d40a08190b7682d8ef8075421 |
completed | March 1, 2026, 10:19 p.m. |
Created at: March 1, 2026, 7:46 p.m.