Triple
T13589238
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | concours d’entrée de l’École Polytechnique |
E324647
|
entity |
| Predicate | sélectivité |
P10787
|
FINISHED |
| Object | très forte |
—
|
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: très forte | Statement: [concours d’entrée de l’École Polytechnique, sélectivité, très forte]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sélectivité Context triple: [concours d’entrée de l’École Polytechnique, sélectivité, très forte]
-
A.
isSelective
chosen
Indicates that the relationship or action involves choosing or affecting only certain specific entities or options while excluding others based on particular criteria.
-
B.
selectionCharacteristic
Indicates a distinguishing feature or criterion used to choose or differentiate one entity from others.
-
C.
selectedAt
Indicates that an entity was chosen or picked at a specific point in time or under particular selection conditions.
-
D.
arity
Indicates the number of arguments or participants that a relation or function takes.
-
E.
selectionRitual
Indicates a process or ceremony through which one or more entities are chosen from a set of candidates.
- 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_69d80769100c819099111274614f5ed2 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbb055cc98819091fab597b69e5e3e |
completed | April 12, 2026, 2:46 p.m. |
| PD | Predicate disambiguation | batch_69dbae18eaf48190809e8b365856cde9 |
completed | April 12, 2026, 2:37 p.m. |
Created at: April 9, 2026, 9:49 p.m.