Triple
T11066888
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Le Raincy |
E261647
|
entity |
| Predicate | notablePeriodOfDevelopment |
P561
|
FINISHED |
| Object | 19th century |
—
|
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: 19th century | Statement: [Le Raincy, notablePeriodOfDevelopment, 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notablePeriodOfDevelopment Context triple: [Le Raincy, notablePeriodOfDevelopment, 19th century]
-
A.
historicalPeriodOfSignificance
Indicates the time period during which an entity is considered to have had its most important or influential historical impact.
-
B.
notableEra
chosen
Indicates the historical period or era for which an entity is especially recognized or significant.
-
C.
wasDevelopedInPeriod
Indicates that something was created, produced, or brought into existence during a specified time period.
-
D.
notableWorkPeriod
Indicates the time span during which an entity produced or was associated with its most significant or well-known works.
-
E.
notableDesignPeriodStart
Indicates the point in time when a subject’s particularly significant or influential design period begins.
- 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_69d6aa98650481908609c7c56bfa7902 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d79920428c81908db824ab54e08e8d |
completed | April 9, 2026, 12:18 p.m. |
| PD | Predicate disambiguation | batch_69d74411d9e881908c0eeafa0f38e4b6 |
completed | April 9, 2026, 6:15 a.m. |
Created at: April 8, 2026, 9:26 p.m.