Triple
T3274558
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paulus Potter |
E68727
|
entity |
| Predicate | signatureMotif |
P15592
|
FINISHED |
| Object | cows |
—
|
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: cows | Statement: [Paulus Potter, signatureMotif, cows]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: signatureMotif Context triple: [Paulus Potter, signatureMotif, cows]
-
A.
signature
Indicates that one entity has provided an official or personal signed endorsement, authorization, or acknowledgment on or for another entity.
-
B.
metricSignature
Indicates that one mathematical object (typically a metric or space) has a specific signature characterizing the signs and multiplicities of its metric components.
-
C.
signatureStyle
Indicates the characteristic way in which an entity typically signs its name or marks documents, distinguishing its unique signing pattern or format.
-
D.
signatureImage
Indicates that an entity has an associated image that visually represents its signature.
-
E.
signatureTheme
chosen
Indicates that something serves as a distinctive, defining theme strongly associated with a particular entity or context.
- 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_69ad859b54f881909bf530d549caf2fd |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adaff8a440819092509bc8511b2785 |
completed | March 8, 2026, 5:20 p.m. |
| PD | Predicate disambiguation | batch_69ada420167c81909b6e2702db296d9e |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:10 p.m.