Triple
T8456522
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Phrygian |
E199931
|
entity |
| Predicate | epigraphicContext |
P9127
|
FINISHED |
| Object | funerary inscriptions |
—
|
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: funerary inscriptions | Statement: [Phrygian, epigraphicContext, funerary inscriptions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: epigraphicContext Context triple: [Phrygian, epigraphicContext, funerary inscriptions]
-
A.
epigraphicType
Indicates the specific kind or category of an inscription as classified in epigraphic studies.
-
B.
scriptOfInscription
Indicates the writing system or script in which a given inscription is written.
-
C.
pyramidTextInscriptions
Indicates that the subject has text inscriptions located on or within a pyramid.
-
D.
mainContentOfInscriptions
chosen
Indicates that something represents the primary textual or symbolic content conveyed by a set of inscriptions.
-
E.
iconographicTextSource
Indicates that a text serves as the source or basis for the content, meaning, or interpretation of an iconographic representation.
- 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_69ca8318231881908fd1bc1c4d45d286 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe48f180c8190a71cf9d7248ade60 |
completed | March 31, 2026, 3:13 p.m. |
| PD | Predicate disambiguation | batch_69cbd0fc634481909842c0a30077bfde |
completed | March 31, 2026, 1:49 p.m. |
Created at: March 30, 2026, 6:10 p.m.