Triple
T23003070
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Edam cheese |
E572682
|
entity |
| Predicate | typicalConsumerMarket |
P89717
|
FINISHED |
| Object | global |
—
|
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: global | Statement: [Edam cheese, typicalConsumerMarket, global]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalConsumerMarket Context triple: [Edam cheese, typicalConsumerMarket, global]
-
A.
isConsumerOriented
Indicates that something is designed, targeted, or tailored primarily to meet the needs, preferences, or interests of consumers.
-
B.
typicalGadgets
Indicates that the associated items are commonly used or standard gadgets typically found or expected in a given context.
-
C.
coversMarket
chosen
Indicates that one entity operates in, serves, or has business presence within a particular market or geographic/sectoral area.
-
D.
marketPreference
Indicates a relationship where one entity favors, targets, or prioritizes a particular market or market segment over others.
-
E.
targetConsumerNeed
Indicates that something is intended to address, satisfy, or be directed toward a specific need or requirement of a consumer.
- 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_69e245b6a3ac81908087599eefe3e365 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f183549bdc81908fdcd44e2c92f7c4 |
completed | April 29, 2026, 4:04 a.m. |
| PD | Predicate disambiguation | batch_69ef3b9cd5488190bcd23183179f48cd |
completed | April 27, 2026, 10:34 a.m. |
Created at: April 17, 2026, 3:50 p.m.