Triple
T29027635
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WoO 3 |
E737636
|
entity |
| Predicate | usedInScholarlyEditions |
P20102
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [WoO 3, usedInScholarlyEditions, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInScholarlyEditions Context triple: [WoO 3, usedInScholarlyEditions, yes]
-
A.
hasScholarlyEdition
Indicates that an entity has an associated scholarly (critically edited and annotated) edition prepared according to academic standards.
-
B.
usedInManuscripts
Indicates that something (such as a term, symbol, or feature) appears or is employed within one or more manuscripts.
-
C.
scholarlyUse
Indicates that something is used for academic, educational, or research-related purposes.
-
D.
usedInCriticalEditions
chosen
Indicates that something (such as a text, source, or variant) is employed as authoritative material in the preparation of critical editions.
-
E.
scholarlyApparatus
Indicates the relationship in which a work provides critical tools—such as notes, commentary, or references—that support, explain, or contextualize another text or body of material.
- 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_69f077ef00fc81909325f084ad37c035 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f7bbf906d8819099020e548dd56bc9 |
completed | May 3, 2026, 9:19 p.m. |
| PD | Predicate disambiguation | batch_69f7b9a2dcf88190a7c9e109e41267be |
completed | May 3, 2026, 9:09 p.m. |
Created at: April 28, 2026, 9:53 a.m.