Triple
T679748
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eve Jobs |
E13154
|
entity |
| Predicate | appearedInCampaign |
P795
|
FINISHED |
| Object | Louis Vuitton digital campaign |
—
|
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: Louis Vuitton digital campaign | Statement: [Eve Jobs, appearedInCampaign, Louis Vuitton digital campaign]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appearedInCampaign Context triple: [Eve Jobs, appearedInCampaign, Louis Vuitton digital campaign]
-
A.
partOfCampaign
Indicates that an entity participates in, belongs to, or is included within a specific campaign.
-
B.
appearsIn
chosen
Indicates that an entity is present, featured, or occurs within a particular context, work, or medium.
-
C.
battledIn
Indicates that two or more entities engaged in a battle or conflict that took place at a specific location or during a particular event.
-
D.
occurredIn
Indicates that an event or action took place within a specific location, context, or time frame.
-
E.
capturedIn
Indicates that one entity was taken prisoner, seized, or otherwise brought under control within the context, location, or event represented by another 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_69a4933d3bf88190972041cd8cf143b9 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a4a04f4efc819082767a7517fa760a |
completed | March 1, 2026, 8:23 p.m. |
| PD | Predicate disambiguation | batch_69a49d1d79608190a849ba9ffad2879d |
completed | March 1, 2026, 8:10 p.m. |
Created at: March 1, 2026, 7:36 p.m.