Triple
T8330140
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Codex Laudianus (E 08) |
E195053
|
entity |
| Predicate | siglum |
P45477
|
FINISHED |
| Object | E 08 |
—
|
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: E 08 | Statement: [Codex Laudianus (E 08), siglum, E 08]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: siglum Context triple: [Codex Laudianus (E 08), siglum, E 08]
-
A.
hasSiglum
chosen
Indicates that an entity is associated with a specific siglum, i.e., a standardized abbreviated symbol or code used to identify it.
-
B.
seal
Indicates that an agent closes or fastens something so that it is securely shut and often airtight or watertight.
-
C.
sillage
Indicates the lingering trail or trace left behind by something (such as a scent, movement, or presence) as it moves through space.
-
D.
signature
Indicates that one entity has provided an official or personal signed endorsement, authorization, or acknowledgment on or for another entity.
-
E.
USSignatory
Indicates that an entity is a party that has formally signed or agreed to a treaty, agreement, or document on behalf of or under the jurisdiction of the United States.
- 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_69ca82e87f2c8190bdb71ee29dfc642d |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb7fb995508190b2ca94ad45bf6d24 |
completed | March 31, 2026, 8:03 a.m. |
| PD | Predicate disambiguation | batch_69cb70c3231c81909e3d463192c9de22 |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 5:56 p.m.