Triple
T3203219
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cotton Nero A.x |
E67098
|
entity |
| Predicate | scriptoriumStatus |
P46129
|
FINISHED |
| Object | unknown |
—
|
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: unknown | Statement: [Cotton Nero A.x, scriptoriumStatus, unknown]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scriptoriumStatus Context triple: [Cotton Nero A.x, scriptoriumStatus, unknown]
-
A.
scriptorium
Indicates that an entity is a place or facility where texts are written, copied, or produced, typically by scribes.
-
B.
writingsStatus
Indicates the status or condition of a set of writings (e.g., whether they are drafted, reviewed, published, or otherwise processed) in relation to an entity.
-
C.
notabilityStatus
Indicates whether and how an entity is recognized as notable or significant within a given context or system.
-
D.
writingSystemStatus
Indicates the current functional or sociolinguistic state of a writing system, such as whether it is actively used, obsolete, official, or endangered.
-
E.
manuscriptStatus
Indicates the current state or phase of a manuscript within its creation, review, or publication process.
- 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_69ad8589bd988190afa7ed2bdffb7b33 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada9b188a88190b7b5e9b3be9410db |
completed | March 8, 2026, 4:54 p.m. |
| PD | Predicate disambiguation | batch_69ad9e078f7c8190813d9fcb4f5071fb |
completed | March 8, 2026, 4:04 p.m. |
| PDg | Predicate description generation | batch_69ada0f9259c8190afbc5ad0fa55436b |
completed | March 8, 2026, 4:16 p.m. |
Created at: March 8, 2026, 3:07 p.m.