Triple
T1292069
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gregorian chant |
E27568
|
entity |
| Predicate | scaleSystem |
P730
|
FINISHED |
| Object | modal |
—
|
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: modal | Statement: [Gregorian chant, scaleSystem, modal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scaleSystem Context triple: [Gregorian chant, scaleSystem, modal]
-
A.
marginSystem
Indicates a financial arrangement where securities are bought or held using borrowed funds, with the securities themselves serving as collateral under a defined margin framework.
-
B.
operationScale
Indicates the relative size, scope, or magnitude at which an operation or activity is conducted.
-
C.
packageSystem
Indicates a relationship where an item or component is organized, bundled, or managed within a particular packaging or distribution system.
-
D.
system
chosen
Indicates that an entity functions as or belongs to a structured, organized set of components or processes that operate together as a system.
-
E.
scaleComparison
Indicates a relationship where two or more entities are compared in terms of their size, magnitude, or scale relative to one another.
- 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_69a496d4ec448190ad653b2590c46711 |
completed | March 1, 2026, 7:43 p.m. |
| NER | Named-entity recognition | batch_69a4c0d7d15081909d3af19b9297f1cc |
completed | March 1, 2026, 10:42 p.m. |
| PD | Predicate disambiguation | batch_69a4bee41ca08190b0ad6f7ea40c0b62 |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:51 p.m.