Triple
T10711965
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Adeline |
E252557
|
entity |
| Predicate | setInHistoricalPeriod |
P41036
|
FINISHED |
| Object | 18th-century France |
—
|
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: 18th-century France | Statement: [Adeline, setInHistoricalPeriod, 18th-century France]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: setInHistoricalPeriod Context triple: [Adeline, setInHistoricalPeriod, 18th-century France]
-
A.
settingDepictedPeriod
Indicates the historical or temporal period in which the setting of something (e.g., a work or scene) is depicted.
-
B.
locatedInHistoricPeriod
chosen
Indicates that an entity exists, occurs, or is situated within a specific historic period or era.
-
C.
hasHistoryPeriod
Indicates that something is associated with, belongs to, or occurs within a specific historical period or era.
-
D.
hasNearbyHistoricPeriod
Indicates that one historic period occurs close in time or space to another historic period.
-
E.
historicalPeriodOfUse
Indicates the time period during which something was in active use or commonly utilized.
- 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_69d6aa5cbabc8190973e683950d89faf |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d6fe533ec081909eafab85f6f6d6b9 |
completed | April 9, 2026, 1:18 a.m. |
| PD | Predicate disambiguation | batch_69d6f30455888190b77f476b8418eaee |
completed | April 9, 2026, 12:29 a.m. |
Created at: April 8, 2026, 9:13 p.m.