Triple
T16934517
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kartuli |
E410793
|
entity |
| Predicate | partnerInteraction |
P124805
|
FINISHED |
| Object | non-contact or minimal-contact dance |
—
|
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: non-contact or minimal-contact dance | Statement: [Kartuli, partnerInteraction, non-contact or minimal-contact dance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partnerInteraction Context triple: [Kartuli, partnerInteraction, non-contact or minimal-contact dance]
-
A.
cooperationPartner
Indicates that two entities are engaged in a collaborative relationship, working together toward shared goals or mutual benefit.
-
B.
partnerNation
Indicates that one entity is recognized as a collaborating or allied nation in relation to another entity.
-
C.
partnerStudio
Indicates that one entity serves as a partner studio associated with, collaborating with, or officially linked to another entity.
-
D.
partnerAgency
Indicates a formal collaborative relationship in which one agency acts as a partner to another agency.
-
E.
segmentPartner
Indicates a partnership relationship between entities within a specific segment, context, or category.
- F. None of above. chosen
Provenance (4 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_69d886c886688190967be07322597ac9 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3cf2899608190a6bacdce9d4ceb84 |
completed | April 18, 2026, 6:36 p.m. |
| PD | Predicate disambiguation | batch_69e32b982f548190b08414d55810de19 |
completed | April 18, 2026, 6:58 a.m. |
| PDg | Predicate description generation | batch_69e32d7aae948190bc238d765795688c |
completed | April 18, 2026, 7:06 a.m. |
Created at: April 10, 2026, 5:30 a.m.