Triple
T10263521
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Camel No. 9 |
E240658
|
entity |
| Predicate | marketedToward |
P55993
|
FINISHED |
| Object | young adult women |
—
|
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: young adult women | Statement: [Camel No. 9, marketedToward, young adult women]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: marketedToward Context triple: [Camel No. 9, marketedToward, young adult women]
-
A.
marketedFor
Indicates that something is promoted, advertised, or positioned as being intended or suitable for a particular use, audience, or purpose.
-
B.
targetMarket
Indicates the group of consumers or organizations that a product, service, or campaign is specifically intended and designed to reach.
-
C.
hasMarketingTarget
chosen
Indicates that an entity is aimed at or intended to appeal to a specific marketing audience or segment.
-
D.
aimedAtBy
Indicates that one entity serves as the target or goal toward which another entity directs an action, intention, or focus.
-
E.
marketedFrom
Indicates that a product, service, or offering began to be marketed starting from a specified time or date.
- 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_69d381a7e198819090280d5ab885d59e |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4d2872830819080fdfa816167d04c |
completed | April 7, 2026, 9:46 a.m. |
| PD | Predicate disambiguation | batch_69d4d1ef6e6c81908a8ee52e4d28127b |
completed | April 7, 2026, 9:44 a.m. |
Created at: April 6, 2026, 11:33 a.m.