Triple
T29824995
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Koliada |
E757353
|
entity |
| Predicate | involvesExchange |
P178182
|
FINISHED |
| Object | gifts |
—
|
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: gifts | Statement: [Koliada, involvesExchange, gifts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: involvesExchange Context triple: [Koliada, involvesExchange, gifts]
-
A.
isExchangedVia
Indicates that something is transferred or traded from one party to another through a specified medium, channel, or mechanism.
-
B.
involvesCurrency
Indicates that the relationship or action includes or pertains to the use, exchange, or specification of a particular currency.
-
C.
tradeInvolves
chosen
Indicates that a trade or exchange relationship exists between the referenced entities, where goods, services, or value are transferred among them.
-
D.
exchanged
Indicates a reciprocal transfer of something (such as information, goods, or services) between two or more entities.
-
E.
relatedExchange
Indicates that there is a connection or association between two exchanges or exchange-related events.
- 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_69f22457c84c8190a6d9f56bc74082a9 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69fba2877b248190a974eb092243c0c4 |
completed | May 6, 2026, 8:20 p.m. |
| PD | Predicate disambiguation | batch_69fb8d06a1b48190a937aa410d159dfa |
completed | May 6, 2026, 6:48 p.m. |
Created at: April 29, 2026, 5:31 p.m.