Triple
T11167593
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Losing You |
E264201
|
entity |
| Predicate | fromEP |
P12978
|
FINISHED |
| Object | True |
—
|
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: True | Statement: [Losing You, fromEP, True]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fromEP Context triple: [Losing You, fromEP, True]
-
A.
EP
Indicates a relationship where one entity is an executive producer (EP) of another entity, typically bearing primary production responsibility or credit.
-
B.
hasEP
Indicates that an entity possesses, is associated with, or is characterized by a specific EP (e.g., an endpoint, event point, or designated EP resource) in the given context.
-
C.
CEP
Indicates a relationship where one entity serves as the central or primary point (e.g., center, hub, or focal element) in relation to another entity or set of entities.
-
D.
export
Indicates that one entity sends goods, services, or data out from its own domain or territory to another entity or external destination.
-
E.
from
chosen
Indicates that something originates, is sent, or is derived from a particular source or starting point.
- 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_69d6aa9dafac8190bd90d2c74f661aa7 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e88843cc81909e503f0921c6d297 |
completed | April 9, 2026, 5:57 p.m. |
| PD | Predicate disambiguation | batch_69d75cf0e6e88190973694abe2990973 |
completed | April 9, 2026, 8:01 a.m. |
Created at: April 8, 2026, 9:29 p.m.