Triple
T16383570
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Early Modern French |
E397866
|
entity |
| Predicate | featureChange |
P123179
|
FINISHED |
| Object | stabilization of French orthography |
—
|
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: stabilization of French orthography | Statement: [Early Modern French, featureChange, stabilization of French orthography]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featureChange Context triple: [Early Modern French, featureChange, stabilization of French orthography]
-
A.
featureAdded
Indicates that a new feature has been introduced or incorporated into a system, product, or entity.
-
B.
featureRemoved
Indicates that a previously existing feature has been taken out, disabled, or is no longer available.
-
C.
featuresAction
Indicates that one entity includes, presents, or showcases a particular action as a notable characteristic or component.
-
D.
changesRequirement
Indicates that one entity modifies, updates, or alters the requirements associated with another entity.
-
E.
featuresSetting
Indicates that something includes, presents, or highlights a particular setting as a notable or primary aspect.
- 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_69d87f2880b48190ae1a9673a3bbef80 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e319de83248190b5d43646fa9b6cda |
completed | April 18, 2026, 5:42 a.m. |
| PD | Predicate disambiguation | batch_69e226f94dd48190b7b8e0e983738a67 |
completed | April 17, 2026, 12:26 p.m. |
| PDg | Predicate description generation | batch_69e24555bb6c8190977cf5c5f9149056 |
completed | April 17, 2026, 2:36 p.m. |
Created at: April 10, 2026, 5:08 a.m.