Triple
T31712198
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | San DiFrangeles |
E809355
|
entity |
| Predicate | usedByCreatorsAs |
P91478
|
FINISHED |
| Object | generic Southern California backdrop |
—
|
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: generic Southern California backdrop | Statement: [San DiFrangeles, usedByCreatorsAs, generic Southern California backdrop]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedByCreatorsAs Context triple: [San DiFrangeles, usedByCreatorsAs, generic Southern California backdrop]
-
A.
usedByCreators
chosen
Indicates that something is utilized or employed by creators in their work or activities.
-
B.
wasUsedBy
Indicates that something served as a tool, resource, or means for an agent to perform an action or achieve a result.
-
C.
areUsedBy
Indicates that certain entities serve as tools, resources, or means that are utilized or employed by other entities.
-
D.
usedByAuthorTo
Indicates that something is employed or utilized by an author to achieve a particular purpose or effect.
-
E.
describedByCreatorAs
Indicates that an entity is characterized or defined in a particular way according to the creator’s own description.
- 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_69f348df4e048190a4a5a9932ada78d6 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f7cec454a88190a9f3bbee2b856636 |
completed | May 3, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69f7c8977c288190997a892ec5f756ed |
completed | May 3, 2026, 10:13 p.m. |
Created at: April 30, 2026, 11:16 p.m.