Triple
T27361235
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Les Amoureuses |
E685828
|
entity |
| Predicate | marketDemand |
P90841
|
FINISHED |
| Object | very high |
—
|
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: very high | Statement: [Les Amoureuses, marketDemand, very high]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: marketDemand Context triple: [Les Amoureuses, marketDemand, very high]
-
A.
demand
Indicates that one entity requests or insists that another entity provide something or perform an action, often with an expectation of compliance.
-
B.
marketSize
chosen
Indicates the total volume or value of demand for a product, service, or market segment within a defined scope (such as a time period or geographic region).
-
C.
marketModel
Indicates the specific economic or pricing framework under which transactions or interactions in a market are structured and governed.
-
D.
demandSide
Indicates a relationship where an entity represents or pertains to the consumer or buyer side of a market, focusing on demand rather than supply.
-
E.
marketFunction
Indicates that an entity serves a particular role or performs a specific function within a market or economic system.
- 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_69ef14887c288190931b8431fdbf53c4 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f6562fd3488190be1acd8c526a28d2 |
completed | May 2, 2026, 7:53 p.m. |
| PD | Predicate disambiguation | batch_69f651a931748190a637e631a52bbfaa |
completed | May 2, 2026, 7:34 p.m. |
Created at: April 27, 2026, 11:53 a.m.