Triple
T15834044
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Caviar |
E383940
|
entity |
| Predicate | restaurantPartners |
P282
|
FINISHED |
| Object | independent restaurants |
—
|
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: independent restaurants | Statement: [Caviar, restaurantPartners, independent restaurants]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: restaurantPartners Context triple: [Caviar, restaurantPartners, independent restaurants]
-
A.
cooperationPartner
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.
partnerNation
Indicates that one entity is recognized as a collaborating or allied nation in relation to another entity.
-
D.
expansionPartner
Indicates a relationship where one entity collaborates with another to support or drive its growth into new markets, regions, or domains.
-
E.
businessPartner
chosen
Indicates a formal collaborative relationship between two entities that work together in a business context, typically sharing responsibilities, risks, or benefits.
- 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_69d86da34c888190976e06c4019d415a |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e11e6670d48190a456581dd951f168 |
completed | April 16, 2026, 5:37 p.m. |
| PD | Predicate disambiguation | batch_69e005418f588190824d91ff7974dada |
completed | April 15, 2026, 9:38 p.m. |
Created at: April 10, 2026, 4:49 a.m.