Triple
T16149987
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LCL |
E391884
|
entity |
| Predicate | typeOfEdition |
P24021
|
FINISHED |
| Object | parallel-text edition |
—
|
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-text edition | Statement: [LCL, typeOfEdition, parallel-text edition]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfEdition Context triple: [LCL, typeOfEdition, parallel-text edition]
-
A.
hasEditionType
chosen
Indicates that one entity is a specific edition type or format classification of another entity (such as a work, publication, or product).
-
B.
edition
Indicates that one entity is a specific version, issue, or release of another (typically a work such as a book, journal, or software).
-
C.
editionPattern
Indicates a recurring structure or template that characterizes how different editions or versions of something are organized or produced.
-
D.
editionNumber
Indicates the specific sequential number assigned to an edition of a work within its series of published versions.
-
E.
hasEditionIn
Indicates that one entity has a specific edition or version that exists or is available in another entity (such as a particular format, language, or location).
- 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_69d87f1c65e48190aa2b4c472e9bafc4 |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e21d9724808190a8332987583a345a |
completed | April 17, 2026, 11:46 a.m. |
| PD | Predicate disambiguation | batch_69e182885bc08190822ae7e8a4b8ac1f |
completed | April 17, 2026, 12:44 a.m. |
Created at: April 10, 2026, 5:01 a.m.