Triple
T21464628
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | You’ve Got That Look |
E529561
|
entity |
| Predicate | basedOnSourceType |
P75726
|
FINISHED |
| Object | original song for film |
—
|
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: original song for film | Statement: [You’ve Got That Look, basedOnSourceType, original song for film]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: basedOnSourceType Context triple: [You’ve Got That Look, basedOnSourceType, original song for film]
-
A.
usesSourceType
Indicates that one entity makes use of, relies on, or operates based on a particular type or category of source.
-
B.
basedOnType
Indicates that one entity is derived, determined, or classified according to the type or category of another entity.
-
C.
mainSourceType
chosen
Indicates the primary category or kind of source from which something originates or is derived.
-
D.
basedOnResource
Indicates that one entity is derived from, created using, or conceptually dependent on another entity as its underlying resource.
-
E.
basedOnBy
Indicates that one entity is derived from, justified by, or constructed using another entity as its source, foundation, or reference.
- 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_69e0c458133481908ae8b41a12c4edec |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69e9e9f100fc819093999018f7d78443 |
completed | April 23, 2026, 9:44 a.m. |
| PD | Predicate disambiguation | batch_69e631df1b38819088d3604854e697b4 |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:09 p.m.