Triple
T10060558
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apedemak |
E212975
|
entity |
| Predicate | scriptAttestedIn |
P46409
|
FINISHED |
| Object | Meroitic hieroglyphic 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: Meroitic hieroglyphic inscriptions | Statement: [Apedemak, scriptAttestedIn, Meroitic hieroglyphic inscriptions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scriptAttestedIn Context triple: [Apedemak, scriptAttestedIn, Meroitic hieroglyphic inscriptions]
-
A.
scriptOfAttestation
chosen
Indicates the writing system or script in which an attestation (recorded instance) of something is written.
-
B.
alsoAttestedIn
Indicates that the same item, fact, or phenomenon is recorded or evidenced in another source, context, or location as well.
-
C.
attestedBy
Indicates that the existence, occurrence, or validity of something is supported, confirmed, or documented by a specified source or authority.
-
D.
attestedAs
Indicates that something is documented, recorded, or certified as having a particular status, form, or property.
-
E.
attestedFrom
Indicates the earliest point in time or source from which something is documented, recorded, or evidenced as existing or in use.
- 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_69ca83977128819084084eb7d1d8c52a |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cdcfd0d23081909510785ef8a186a3 |
completed | April 2, 2026, 2:09 a.m. |
| PD | Predicate disambiguation | batch_69cd4b92573481909389bc6148ae7ea8 |
completed | April 1, 2026, 4:45 p.m. |
Created at: March 30, 2026, 8:57 p.m.