Triple
T18563924
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ancient Greek Musical Notation |
E453713
|
entity |
| Predicate | hasScriptPropertyValue |
P132518
|
FINISHED |
| Object | Script=Common |
—
|
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: Script=Common | Statement: [Ancient Greek Musical Notation, hasScriptPropertyValue, Script=Common]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasScriptPropertyValue Context triple: [Ancient Greek Musical Notation, hasScriptPropertyValue, Script=Common]
-
A.
hasScriptCode
Indicates that an entity is associated with a particular writing system identified by a specific script code.
-
B.
containsScript
Indicates that one entity includes or embeds the script of another entity within it.
-
C.
hasScriptStatus
Indicates that an entity has a particular script-related state or condition, such as whether a script is present, active, or in a given status.
-
D.
hasScriptTool
Indicates that an entity uses, is associated with, or is supported by a particular scripting tool or scripting environment.
-
E.
hasScriptUsage
Indicates that one entity uses, employs, or is written in the script or writing system specified by another entity.
- 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_69d8d38974308190a9174430ef256b73 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e53afc57448190abd90167d7e12a18 |
completed | April 19, 2026, 8:28 p.m. |
| PD | Predicate disambiguation | batch_69e478c16e0c8190b03966aa23c395a6 |
completed | April 19, 2026, 6:40 a.m. |
| PDg | Predicate description generation | batch_69e484121cd48190bf583b4c94636a30 |
completed | April 19, 2026, 7:28 a.m. |
Created at: April 10, 2026, 11:42 a.m.