Triple
T27782644
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Texaco gas station (Hill Valley) |
E699373
|
entity |
| Predicate | depictsBrandPlacement |
P101226
|
FINISHED |
| Object | Texaco |
—
|
NE NERFINISHED |
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: Texaco | Statement: [Texaco gas station (Hill Valley), depictsBrandPlacement, Texaco]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: depictsBrandPlacement Context triple: [Texaco gas station (Hill Valley), depictsBrandPlacement, Texaco]
-
A.
featuresProductPlacementFor
chosen
Indicates that one entity includes or showcases another entity as a product placement within its content.
-
B.
logoPlacement
Indicates the spatial or contextual position where a logo is displayed or applied in relation to another object, surface, or medium.
-
C.
sponsorPlacement
Indicates that one entity financially supports or endorses another entity in exchange for a specified form of promotional placement.
-
D.
sponsorshipBrand
Indicates that one entity serves as a sponsoring brand for another entity, typically providing support, funding, or endorsement.
-
E.
depictsName
Indicates that something visually represents or portrays the name of an entity.
- 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_69ef6a4b5a9081909c9111396c2be3d2 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f68805b4848190b75da14996d52a38 |
completed | May 2, 2026, 11:25 p.m. |
| PD | Predicate disambiguation | batch_69f68609c0b08190a8e1238a4d97c270 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 27, 2026, 5:11 p.m.