Triple
T17547459
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Claude Gelée |
E427364
|
entity |
| Predicate | signaturePractice |
P127873
|
FINISHED |
| Object | recorded paintings in a Liber Veritatis |
—
|
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: recorded paintings in a Liber Veritatis | Statement: [Claude Gelée, signaturePractice, recorded paintings in a Liber Veritatis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: signaturePractice Context triple: [Claude Gelée, signaturePractice, recorded paintings in a Liber Veritatis]
-
A.
signatureConcept
Indicates that one concept is the defining or characteristic idea that most distinctly represents or identifies another concept.
-
B.
signatureWork
Indicates that the work is a defining or most representative creation associated with an entity (such as a person, group, or organization).
-
C.
signature
Indicates that one entity has provided an official or personal signed endorsement, authorization, or acknowledgment on or for another entity.
-
D.
signatureEvent
Indicates an event in which an entity formally signs or authorizes something, such as a document, agreement, or record.
-
E.
signText
Indicates that a sign bears or displays a particular textual content.
- 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_69d889df6dc081908f67dbadc03c07ee |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e454626cfc8190a2602ba4934b8e6d |
completed | April 19, 2026, 4:04 a.m. |
| PD | Predicate disambiguation | batch_69e3b4fb39948190a82a597c5bac5c57 |
completed | April 18, 2026, 4:44 p.m. |
| PDg | Predicate description generation | batch_69e3bbb37d148190b7f38599c06594ee |
completed | April 18, 2026, 5:13 p.m. |
Created at: April 10, 2026, 5:49 a.m.