Triple
T10816054
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CIVB |
E255229
|
entity |
| Predicate | promotesInMarket |
P5087
|
FINISHED |
| Object | domestic French market |
—
|
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: domestic French market | Statement: [CIVB, promotesInMarket, domestic French market]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: promotesInMarket Context triple: [CIVB, promotesInMarket, domestic French market]
-
A.
promotedIn
Indicates that an entity was advanced to a higher rank, position, or status during a specified time or event.
-
B.
promotes
Indicates that one entity actively supports, advances, or encourages the growth, adoption, or success of another entity or outcome.
-
C.
promotionalFor
Indicates that one entity serves to advertise, market, or otherwise promote another entity, such as a product, service, event, or brand.
-
D.
marketedFor
chosen
Indicates that something is promoted, advertised, or positioned as being intended or suitable for a particular use, audience, or purpose.
-
E.
promotionDeterminedBy
Indicates that the occurrence or outcome of a promotion is decided or influenced by a specified factor or condition.
- 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_69d6aa8081448190a9324184f2bd1c26 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d733edab248190b2cf7f7bc2684468 |
completed | April 9, 2026, 5:06 a.m. |
| PD | Predicate disambiguation | batch_69d70d1bf3648190b36fa96ea018e0dc |
completed | April 9, 2026, 2:21 a.m. |
Created at: April 8, 2026, 9:18 p.m.