Triple
T12155766
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Adlam script |
E289569
|
entity |
| Predicate | supportsToneMarking |
P67251
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Adlam script, supportsToneMarking, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsToneMarking Context triple: [Adlam script, supportsToneMarking, true]
-
A.
usesToneMarks
Indicates that one entity applies or includes diacritical tone marks in the representation or transcription of another entity (such as text, language, or symbols).
-
B.
toneMarkFunction
Indicates a function or role that assigns, modifies, or interprets tone marks in a tonal or phonetic system.
-
C.
marksTones
chosen
Indicates that one entity applies or denotes tonal markings or distinctions on another entity, such as in language or notation.
-
D.
hasPhonemicTone
Indicates that a language, word, or syllable uses pitch differences (tones) as phonemic contrasts that can change meaning.
-
E.
supportsMarkupStyle
Indicates that one entity is capable of handling, rendering, or otherwise working with a specified markup style associated with another entity.
- 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_69d6ab4c6710819097a9d228382dde43 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d915d7109481908bf5fe512bba3c89 |
completed | April 10, 2026, 3:23 p.m. |
| PD | Predicate disambiguation | batch_69d9150c18148190bf8152189c0e5fca |
completed | April 10, 2026, 3:19 p.m. |
Created at: April 8, 2026, 9:50 p.m.