Triple
T30108088
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Washington Manuscript of the Gospels |
E765184
|
entity |
| Predicate | scriptCharacteristic |
P56672
|
FINISHED |
| Object | majuscule letters |
—
|
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: majuscule letters | Statement: [Washington Manuscript of the Gospels, scriptCharacteristic, majuscule letters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scriptCharacteristic Context triple: [Washington Manuscript of the Gospels, scriptCharacteristic, majuscule letters]
-
A.
artCharacteristics
Indicates a relationship where specific qualities, styles, or features are attributed to a work of art.
-
B.
codeCharacteristic
Indicates that one piece of code possesses a specific property, feature, or quality in relation to another referenced aspect.
-
C.
recordCharacteristic
Indicates that an entity documents or stores a specific characteristic or attribute of another entity.
-
D.
seriesCharacteristic
Indicates that something is a defining feature, attribute, or property associated with a particular series.
-
E.
describesCharacteristicOf
chosen
Indicates that one entity expresses or specifies a characteristic, feature, or property of another entity.
- 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_69f22475ad7c8190be7f9541044a0bbb |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f71996e1a48190ac59a1d66d7c44e8 |
completed | May 3, 2026, 9:47 a.m. |
| PD | Predicate disambiguation | batch_69f71820c6c88190ab38b4fa626d22cc |
completed | May 3, 2026, 9:40 a.m. |
Created at: April 29, 2026, 7:09 p.m.