Triple
T3214244
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vitruvian Man |
E67351
|
entity |
| Predicate | scriptOfNotes |
P46248
|
FINISHED |
| Object | mirror writing |
—
|
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: mirror writing | Statement: [Vitruvian Man, scriptOfNotes, mirror writing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scriptOfNotes Context triple: [Vitruvian Man, scriptOfNotes, mirror writing]
-
A.
topNote
Indicates that one entity serves as the primary or highest-level note associated with another entity.
-
B.
baseNote
Indicates that one entity serves as the fundamental or reference note upon which another musical element (such as a chord, scale, or interval) is built or defined.
-
C.
script
Indicates that an entity is associated with a written text or code (such as a screenplay, program, or written instructions) that defines its content or behavior.
-
D.
scriptOfInscription
Indicates the writing system or script in which a given inscription is written.
-
E.
approachToNotes
Indicates the manner, strategy, or style with which an entity engages with, interprets, or works with notes.
- F. None of above. chosen
Provenance (4 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_69ad858ac36c81909962589cd277d6e2 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69adaabd01d48190be0dc610b9987a25 |
completed | March 8, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69ad9e09b83881908801d79c3d9254f9 |
completed | March 8, 2026, 4:04 p.m. |
| PDg | Predicate description generation | batch_69ada0f9259c8190afbc5ad0fa55436b |
completed | March 8, 2026, 4:16 p.m. |
Created at: March 8, 2026, 3:07 p.m.