Triple
T13589235
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | concours d’entrée de l’École Polytechnique |
E324647
|
entity |
| Predicate | composante |
P14071
|
FINISHED |
| Object | épreuves écrites |
—
|
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: épreuves écrites | Statement: [concours d’entrée de l’École Polytechnique, composante, épreuves écrites]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: composante Context triple: [concours d’entrée de l’École Polytechnique, composante, épreuves écrites]
-
A.
component3
Indicates that one entity is the third component or sub-part within a larger composite structure or system involving another entity.
-
B.
component1
chosen
Indicates that one entity functions as a constituent or part of another entity within a larger whole.
-
C.
compositionalFeature
Indicates that one entity is a structural or constituent feature that forms part of the composition or makeup of another entity.
-
D.
componentFrom
Indicates that one entity is derived from, produced by, or originates as a component of another entity.
-
E.
componentCC
Indicates that one entity is a component or constituent part of another entity within a coordinated or composite construction.
- 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.