Triple
T18587002
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pictish language |
E454259
|
entity |
| Predicate | hasRunicInscriptions |
P16756
|
FINISHED |
| Object | false |
—
|
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: false | Statement: [Pictish language, hasRunicInscriptions, false]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRunicInscriptions Context triple: [Pictish language, hasRunicInscriptions, false]
-
A.
hasLanternInscription
Indicates that an entity bears or contains an inscription specifically on or associated with a lantern.
-
B.
hasGraveInscription
Indicates that an entity (typically a grave or tomb) bears a specific inscription engraved or written on it.
-
C.
hasCarvings
Indicates that one entity features or contains carved designs or engravings on its surface, created by another entity or process.
-
D.
hasNumberOfNamesInscribed
Indicates the quantity of distinct names that are inscribed on a given entity.
-
E.
hasInscriptions
chosen
Indicates that an object, surface, or artifact bears written, carved, or engraved inscriptions on it.
- 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_69d8d38ae7e081908a98df1251842402 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e545b2f20481908da74447cd08d5bd |
completed | April 19, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69e478c98d4c81909d37a0e72c6e7bd0 |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:44 a.m.