Triple
T27550809
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cavaillon melon |
E695493
|
entity |
| Predicate | isConsideredSpecialtyOf |
P165709
|
FINISHED |
| Object | Provence |
—
|
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: Provence | Statement: [Cavaillon melon, isConsideredSpecialtyOf, Provence]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isConsideredSpecialtyOf Context triple: [Cavaillon melon, isConsideredSpecialtyOf, Provence]
-
A.
hasSpecialty
Indicates that an entity possesses a particular area of expertise, focus, or professional specialization.
-
B.
subjectSpecialization
Indicates that one subject focuses on, or has expertise in, a particular field, topic, or area of knowledge.
-
C.
institutionSpecialization
Indicates that an institution focuses on, is dedicated to, or has expertise in a particular field, domain, or area of activity.
-
D.
subDisciplineOf
Indicates that one discipline is a more specialized or narrower field within another, broader discipline.
-
E.
hasSpecialist
Indicates that one entity is associated with or assigned to a specialist entity that provides expert support, service, or oversight for it.
- 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_69ef5386c3e08190bfe33aa326e1f72b |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f65b14512c8190a40e70319dcc54cd |
completed | May 2, 2026, 8:14 p.m. |
| PD | Predicate disambiguation | batch_69f659ce58408190ba9e007b4810d4d0 |
completed | May 2, 2026, 8:08 p.m. |
| PDg | Predicate description generation | batch_69f65a6babcc81908052c9907a99c882 |
completed | May 2, 2026, 8:11 p.m. |
Created at: April 27, 2026, 1:34 p.m.