Triple
T3173662
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | French grandes écoles |
E66410
|
entity |
| Predicate | notableFieldCluster |
P39276
|
FINISHED |
| Object | écoles d’ingénieurs |
—
|
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: écoles d’ingénieurs | Statement: [French grandes écoles, notableFieldCluster, écoles d’ingénieurs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableFieldCluster Context triple: [French grandes écoles, notableFieldCluster, écoles d’ingénieurs]
-
A.
notableField
chosen
Indicates the field, discipline, or area of activity for which an entity is especially known or distinguished.
-
B.
notableCenter
Indicates that an entity is recognized as an important or prominent central point, hub, or focal location for another entity or activity.
-
C.
notableTarget
Indicates that the subject is particularly significant, prominent, or noteworthy with respect to the specified target.
-
D.
notableIndexFamily
Indicates that an entity is recognized as a particularly important or prominent member within a specified family group.
-
E.
notableFinding
Indicates that an observation, result, or piece of evidence is considered significant or noteworthy in the given context.
- 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_69ad8586a34c8190944c63ec11a8de1a |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada66facf881908b9ec687d68ce91b |
completed | March 8, 2026, 4:40 p.m. |
| PD | Predicate disambiguation | batch_69ad9e0076b4819094628f1ad10b8f68 |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:06 p.m.