Triple
T14873209
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Louvre INV 253 |
E349801
|
entity |
| Predicate | associatedWorkCentury |
P20496
|
FINISHED |
| Object | 17th 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: 17th century | Statement: [Louvre INV 253, associatedWorkCentury, 17th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWorkCentury Context triple: [Louvre INV 253, associatedWorkCentury, 17th century]
-
A.
centuryOfWork
chosen
Indicates the century during which a particular work, activity, or contribution primarily took place.
-
B.
associatedWithCentury
Indicates that something has a relevant connection or linkage to a particular century, such as occurring in, belonging to, or being characteristic of that time period.
-
C.
originalCentury
Indicates the century in which something was originally created, produced, or came into existence.
-
D.
declaredInCentury
Indicates that something (such as an event, work, or concept) was formally declared or proclaimed during a specified century.
-
E.
flourishedInCentury
Indicates that an entity experienced its peak activity, influence, or development during a specified century.
- 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_69d822ee4f408190b6ac3b2fa434f0df |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69ded5e2c94c8190a16f05ea81701fc1 |
completed | April 15, 2026, 12:03 a.m. |
| PD | Predicate disambiguation | batch_69de8c1a2bcc81908f914e2e2ced65eb |
completed | April 14, 2026, 6:48 p.m. |
Created at: April 10, 2026, 1:55 a.m.