Triple
T37507865
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brokers |
E932143
|
entity |
| Predicate | dealPartners |
P34923
|
FINISHED |
| Object | Kyrian |
—
|
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: Kyrian | Statement: [Brokers, dealPartners, Kyrian]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dealPartners Context triple: [Brokers, dealPartners, Kyrian]
-
A.
cooperationPartner
chosen
Indicates that two entities are engaged in a collaborative relationship, working together toward shared goals or mutual benefit.
-
B.
exportPartners
Indicates a relationship where one entity collaborates with or serves as a partner to another in exporting goods or services across borders.
-
C.
segmentPartner
Indicates a partnership relationship between entities within a specific segment, context, or category.
-
D.
merchandisingPartner
Indicates a relationship where one party collaborates with another to plan, manage, or execute the promotion, display, or sale of products or services.
-
E.
partnerInteraction
Indicates an interaction or engagement occurring specifically between partners in a relationship or collaboration.
- 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_69f76ec5268481909ea01c73aeeefd42 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fba5eec0448190a5e6f0c43fdcd0e3 |
completed | May 6, 2026, 8:34 p.m. |
| PD | Predicate disambiguation | batch_69fba34edd548190bfa980e6e16e0a88 |
completed | May 6, 2026, 8:23 p.m. |
Created at: May 3, 2026, 4:17 p.m.