Triple
T37623835
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A. v. Ostade |
E936145
|
entity |
| Predicate | typeOfMark |
P5686
|
FINISHED |
| Object | authorship mark |
—
|
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: authorship mark | Statement: [A. v. Ostade, typeOfMark, authorship mark]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfMark Context triple: [A. v. Ostade, typeOfMark, authorship mark]
-
A.
markType
chosen
Indicates the specific category or kind of mark associated with or applied to an entity.
-
B.
languageOfMarking
Indicates the language used for labels, annotations, or other markings associated with an entity.
-
C.
markingDefinition
Indicates that one entity defines the marking, labeling, or classification rules that are applied to another entity.
-
D.
registrationMark
Indicates that an entity bears a specific official registration identifier or code assigned by an authority.
-
E.
isMarkedAccordingTo
Indicates that one entity bears marks, labels, or annotations that conform to the rules, standards, or criteria specified by another entity or reference.
- 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_69f76ed24820819081bafd36e9088701 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a1553e08190bb7424c448cb1f33 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:18 p.m.