Triple
T38225063
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Midas Monument inscription |
E1012118
|
entity |
| Predicate | writingSystemPhase |
P27604
|
FINISHED |
| Object | Old Phrygian |
—
|
NE NERFINISHED |
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: Old Phrygian | Statement: [Midas Monument inscription, writingSystemPhase, Old Phrygian]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: writingSystemPhase Context triple: [Midas Monument inscription, writingSystemPhase, Old Phrygian]
-
A.
writingSystemStage
chosen
Indicates the developmental or historical stage a particular writing system is in or associated with.
-
B.
writingSystemScope
Indicates the range or extent of content, languages, or contexts to which a particular writing system applies or is used.
-
C.
writingSystem
Indicates that one entity is the script or system of written symbols used to represent the language or content of another entity.
-
D.
writingSystemStatus
Indicates the current functional or sociolinguistic state of a writing system, such as whether it is actively used, obsolete, official, or endangered.
-
E.
writingSystemUsedSince
Indicates that a particular writing system has been in use starting from a specified point in time or period.
- 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_69f76dd25e0c81909f2abd0803e5e3ee |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fcc42cbac48190b8d3e4c9ce140838 |
completed | May 7, 2026, 4:56 p.m. |
| PD | Predicate disambiguation | batch_69fcb0fc69c88190800453eb57a7e62c |
completed | May 7, 2026, 3:34 p.m. |
Created at: May 3, 2026, 4:30 p.m.