Triple
T19722319
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Codex Carolinus |
E473640
|
entity |
| Predicate | hasBilingualLayout |
P82135
|
FINISHED |
| Object | parallel Gothic and Latin text |
—
|
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: parallel Gothic and Latin text | Statement: [Codex Carolinus, hasBilingualLayout, parallel Gothic and Latin text]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBilingualLayout Context triple: [Codex Carolinus, hasBilingualLayout, parallel Gothic and Latin text]
-
A.
bilingualLayout
chosen
Indicates a layout or arrangement that simultaneously presents content in two different languages.
-
B.
isBilingual
Indicates that an entity is able to communicate fluently in two distinct languages.
-
C.
isBilingualRegion
Indicates that a region officially uses two languages or has two predominant languages in regular use.
-
D.
languageOnBothSides
Indicates that the same language is used or present on both sides of a given relationship, boundary, or comparison.
-
E.
isMultilingual
Indicates that an entity can understand and/or communicate in multiple languages.
- 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_69d8e517ebd48190979ee76723bcfadf |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e649f587d88190bf519fec7ce634d3 |
completed | April 20, 2026, 3:44 p.m. |
| PD | Predicate disambiguation | batch_69e5304a7aac8190ac13f75f0c008e45 |
completed | April 19, 2026, 7:43 p.m. |
Created at: April 10, 2026, 1:46 p.m.