Triple
T16255483
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cantós de España |
E394615
|
entity |
| Predicate | isWrittenNotation |
P95660
|
FINISHED |
| Object | Western staff notation |
—
|
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: Western staff notation | Statement: [Cantós de España, isWrittenNotation, Western staff notation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isWrittenNotation Context triple: [Cantós de España, isWrittenNotation, Western staff notation]
-
A.
isWritten
Indicates that a text, document, or content has been created or recorded in written form by an agent.
-
B.
typicalNotation
Indicates that one entity is the standard or commonly used symbolic representation (notation) for another entity.
-
C.
isWrittenAs
Indicates that one entity is represented or expressed in written form as another entity (such as a specific spelling, notation, or symbol).
-
D.
usesNotationFor
chosen
Indicates that one entity employs or adopts a particular notation system or symbolic representation for another entity.
-
E.
isWrittenWith
Indicates that something is created or expressed using a particular writing tool, medium, or system.
- 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_69d87f2171208190951025e526947816 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e2459a48f081909c76b38741b8f04e |
completed | April 17, 2026, 2:37 p.m. |
| PD | Predicate disambiguation | batch_69e219f259e88190bf49d8408c04178e |
completed | April 17, 2026, 11:30 a.m. |
Created at: April 10, 2026, 5:04 a.m.