Triple
T13742626
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | D |
E330122
|
entity |
| Predicate | alternativeNotationForSameManuscript |
P57346
|
FINISHED |
| Object | 05 |
—
|
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: 05 | Statement: [D, alternativeNotationForSameManuscript, 05]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: alternativeNotationForSameManuscript Context triple: [D, alternativeNotationForSameManuscript, 05]
-
A.
writtenInSameManuscriptAs
Indicates that two written works or textual items appear together within the same physical or digital manuscript.
-
B.
copiedManuscriptsOf
Indicates that one entity has produced or created handwritten reproductions of the manuscripts belonging to another entity.
-
C.
hasAlternativeNotation
chosen
Indicates that an entity can be represented or written in a different, equivalent form or notation.
-
D.
associatedWithManuscript
Indicates a relationship in which an entity is linked or connected to a particular manuscript, such as by authorship, reference, inclusion, or relevance.
-
E.
areManuscriptsOf
Indicates that the subject entities are manuscripts that are versions, copies, or instances of the work represented by the object entity.
- 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_69d80772315881908f980cae40d91664 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69de020855ec8190a60fa1cb761f2e68 |
completed | April 14, 2026, 8:59 a.m. |
| PD | Predicate disambiguation | batch_69dbbe950b148190ba0df8a749269ec6 |
completed | April 12, 2026, 3:47 p.m. |
Created at: April 9, 2026, 9:55 p.m.