Triple
T34891152
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Le Grand Diplôme |
E1006288
|
entity |
| Predicate | canBeTakenAt |
P197834
|
FINISHED |
| Object | Le Cordon Bleu Paris |
—
|
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: Le Cordon Bleu Paris | Statement: [Le Grand Diplôme, canBeTakenAt, Le Cordon Bleu Paris]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBeTakenAt Context triple: [Le Grand Diplôme, canBeTakenAt, Le Cordon Bleu Paris]
-
A.
mayTake
Indicates that an entity is permitted or allowed to take, enroll in, or participate in another entity (such as a course, resource, or opportunity).
-
B.
canBeTakenQuickly
Indicates that the action or resource can be obtained, completed, or utilized in a short amount of time.
-
C.
canBeUsed
Indicates that one entity is suitable or available to serve a particular function, purpose, or role in relation to another entity or context.
-
D.
canOperateAt
Indicates that one entity has the capability, permission, or suitability to function or perform its role at, within, or under the conditions of another entity or context.
-
E.
canBeHeld
Indicates that an entity is capable of being physically grasped, supported, or carried by another entity.
- 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_69f76dbedb288190afe5780710847410 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69feafa1ba0081909013800b85a9f613 |
completed | May 9, 2026, 3:53 a.m. |
| PD | Predicate disambiguation | batch_69feae58d62c81909d031f3df8992883 |
completed | May 9, 2026, 3:47 a.m. |
| PDg | Predicate description generation | batch_69feafa0acd881908bb6c01635b5537a |
completed | May 9, 2026, 3:53 a.m. |
Created at: May 3, 2026, 4 p.m.