Triple
T10055882
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mn-k3w-Rˁ |
E208859
|
entity |
| Predicate | writtenWithCartouche |
P91863
|
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: [Mn-k3w-Rˁ, writtenWithCartouche, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: writtenWithCartouche Context triple: [Mn-k3w-Rˁ, writtenWithCartouche, true]
-
A.
writtenWithCharacter
Indicates that something is written using a particular character or set of characters as its writing system or notation.
-
B.
writtenForCharacter
Indicates that a piece of writing (such as a script, scene, or dialogue) was specifically created or tailored for a particular character.
-
C.
calligraphicUse
Indicates that one entity uses or applies another entity specifically for calligraphic purposes or in the practice of calligraphy.
-
D.
hasHandwritingOf
Indicates that one entity’s handwriting style or written text is attributed to, or produced by, another entity.
-
E.
writtenIn
Indicates that a work (such as a text, program, or document) is expressed or encoded using a particular language or notation.
- F. None of above. chosen
Provenance (4 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_69ca836094408190a36a1ea7e9a86fcd |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cdcfacacd08190abe66f8bb17b92c7 |
completed | April 2, 2026, 2:08 a.m. |
| PD | Predicate disambiguation | batch_69cd4b92573481909389bc6148ae7ea8 |
completed | April 1, 2026, 4:45 p.m. |
| PDg | Predicate description generation | batch_69cd4f8d9b888190b8067bd916dae773 |
completed | April 1, 2026, 5:02 p.m. |
Created at: March 30, 2026, 8:57 p.m.