Triple
T15802391
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ethiopic manuscripts |
E383127
|
entity |
| Predicate | inkComposition |
P110526
|
FINISHED |
| Object | carbon-based ink |
—
|
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: carbon-based ink | Statement: [Ethiopic manuscripts, inkComposition, carbon-based ink]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inkComposition Context triple: [Ethiopic manuscripts, inkComposition, carbon-based ink]
-
A.
backgroundComposition
Indicates that one entity serves as the background or surrounding setting in which another entity is visually or contextually composed.
-
B.
currentComposition
chosen
Indicates that one entity is presently composed of, or made up from, another entity or set of entities.
-
C.
coComposer
Indicates a relationship where two or more entities jointly compose a musical or artistic work together.
-
D.
compositionDetail
Indicates that one entity specifies or describes the internal makeup, structure, or constituent elements of another entity.
-
E.
specialComposition
Indicates that one entity is composed of another in a distinctive or non-standard way, highlighting a particular or exceptional form of composition between them.
- 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_69d86da16e188190b89af699f1ed0bfe |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e0b523bf508190af4a54bdc983a9a1 |
completed | April 16, 2026, 10:08 a.m. |
| PD | Predicate disambiguation | batch_69e0053b847c8190945726c3ddac21cc |
completed | April 15, 2026, 9:38 p.m. |
Created at: April 10, 2026, 4:48 a.m.