Triple
T33102270
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Geneviève Fontanel |
E847083
|
entity |
| Predicate | hasWorkPeriodEnd |
P195507
|
FINISHED |
| Object | 21st 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: 21st century | Statement: [Geneviève Fontanel, hasWorkPeriodEnd, 21st century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWorkPeriodEnd Context triple: [Geneviève Fontanel, hasWorkPeriodEnd, 21st century]
-
A.
hasWorkPeriod
Indicates that an entity is associated with a specific span of time during which it performs or is engaged in some work or activity.
-
B.
hasWorkPeriodStart
Indicates the point in time when a specified work period begins.
-
C.
containsWorkFromPeriod
Indicates that something includes or features work that originates from a specified historical or temporal period.
-
D.
hasUnstaffedPeriods
Indicates that there are time intervals during which a position, role, or location has no assigned or present staff.
-
E.
hasWorkSchedule
Indicates that an entity is assigned or follows a specific work schedule, defining when they are expected to work.
- 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_69f3495686508190b76bf20fa5e00bf7 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fdd5fba5048190b7d430ae2054a1fd |
completed | May 8, 2026, 12:24 p.m. |
| PD | Predicate disambiguation | batch_69fdd35f76f88190a1854ea27132f9c7 |
completed | May 8, 2026, 12:13 p.m. |
| PDg | Predicate description generation | batch_69fdd5faea908190a17d77e050362ef5 |
completed | May 8, 2026, 12:24 p.m. |
Created at: May 1, 2026, 1:26 a.m.