Triple
T13857037
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CPGE |
E333092
|
entity |
| Predicate | typicalFirstYearName |
P111793
|
FINISHED |
| Object | première année |
—
|
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: première année | Statement: [CPGE, typicalFirstYearName, première année]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalFirstYearName Context triple: [CPGE, typicalFirstYearName, première année]
-
A.
firstYear
Indicates that an entity is in its first year of existence, operation, or participation within a specified context.
-
B.
firstYearComponent
Indicates that something is a component or part that belongs to, occurs in, or is specifically associated with the first year of a larger sequence, program, or period.
-
C.
typicalDegreeName
Indicates the standard or commonly used academic degree title associated with an educational program or qualification.
-
D.
firstGenerationName
Indicates that the specified name is assigned to or associated with the first generation in a sequence, lineage, or series.
-
E.
firstYearUnderCurrentName
Indicates the first year in which an entity began operating or being known under its current name.
- 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_69d81c5ba13c8190839315f54768acfd |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de02dc9f488190b7181dcb7e304632 |
completed | April 14, 2026, 9:03 a.m. |
| PD | Predicate disambiguation | batch_69dbc8691b608190a25a7c70a366b170 |
completed | April 12, 2026, 4:29 p.m. |
| PDg | Predicate description generation | batch_69dcad0eea9881908f71e1eed9a2446b |
completed | April 13, 2026, 8:45 a.m. |
Created at: April 9, 2026, 10:14 p.m.