Triple
T25059678
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Xenia Tchoumitcheva |
E627621
|
entity |
| Predicate | hasOnlineBrand |
P90076
|
FINISHED |
| Object | Xenia Tchoumi |
—
|
NE NERFINISHED |
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: Xenia Tchoumi | Statement: [Xenia Tchoumitcheva, hasOnlineBrand, Xenia Tchoumi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOnlineBrand Context triple: [Xenia Tchoumitcheva, hasOnlineBrand, Xenia Tchoumi]
-
A.
hasOnlineCatalog
Indicates that an entity provides a catalog of its items or offerings that is accessible via the internet.
-
B.
hasBrandPresence
chosen
Indicates that an entity maintains an official or recognizable representation (such as branding, marketing, or products) within a particular context, location, or platform.
-
C.
hasOnlineShop
Indicates that an entity operates or is associated with a shop that sells goods or services via the internet.
-
D.
hasBrandWebsite
Indicates that an entity has an associated official website representing its brand.
-
E.
hasOnlinePlatform
Indicates that an entity operates, maintains, or is associated with a presence or service on an online platform.
- 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_69e2ff2c45f48190afa28369f1df6786 |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f61f12b0f08190bc4a16907941864c |
completed | May 2, 2026, 3:58 p.m. |
| PD | Predicate disambiguation | batch_69f61b37a5648190b10d33ae205ccfee |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 18, 2026, 6:09 a.m.