Triple
T26915154
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heptaméron |
E677496
|
entity |
| Predicate | hasWorkTitleInFrench |
P160063
|
FINISHED |
| Object | L’Heptaméron |
—
|
NE NERFINISHED |
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: L’Heptaméron | Statement: [Heptaméron, hasWorkTitleInFrench, L’Heptaméron]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWorkTitleInFrench Context triple: [Heptaméron, hasWorkTitleInFrench, L’Heptaméron]
-
A.
equivalentTitleInFrench
Indicates that one entity’s title is the equivalent or corresponding title of another entity, specifically expressed in French.
-
B.
hasWorkTitleVariant
chosen
Indicates that an entity has an alternative or variant form of its work title, such as a different wording, spelling, or language version of the same title.
-
C.
hasTitleWork
Indicates that an entity is associated with a specific work by its title (i.e., the entity has or bears that work’s title).
-
D.
hasWorkingTitle
Indicates that an entity is associated with a provisional or temporary title used during its development or production.
-
E.
hasTitleInEnglishOrthography
Indicates that an entity has a specific title expressed using English spelling and writing conventions.
- 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_69eee9bcef1c8190be88586bb902bb9b |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f7221dc9a88190bb8194fcc29c42bc |
completed | May 3, 2026, 10:23 a.m. |
| PD | Predicate disambiguation | batch_69f72153a9188190b02adc84e1be4af8 |
completed | May 3, 2026, 10:20 a.m. |
Created at: April 27, 2026, 6:04 a.m.