Triple
T10291060
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maya hieroglyphs |
E241364
|
entity |
| Predicate | hasWritingType |
P93281
|
FINISHED |
| Object | logographic |
—
|
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: logographic | Statement: [Maya hieroglyphs, hasWritingType, logographic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWritingType Context triple: [Maya hieroglyphs, hasWritingType, logographic]
-
A.
isWritten
Indicates that a text, document, or content has been created or recorded in written form by an agent.
-
B.
writTypes
Indicates the types or categories of writs (formal written legal orders) associated with an action or entity.
-
C.
hasWrittenWorkType
Indicates that an entity (typically a written work) is associated with a specific type or category of written work (such as novel, article, report, etc.).
-
D.
canBeWrittenIn
Indicates that something is capable of being expressed, encoded, or represented using a particular language, notation, or medium.
-
E.
hasWrittenFor
Indicates that one entity has created written content (such as articles, stories, or texts) for or on behalf of another entity, typically a publication, organization, or platform.
- 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_69d381aaafc08190af475ef58dc16aba |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4d7ccb7ec8190a538cf279e48116e |
completed | April 7, 2026, 10:09 a.m. |
| PD | Predicate disambiguation | batch_69d4d1f117708190928f92ae2611d724 |
completed | April 7, 2026, 9:44 a.m. |
| PDg | Predicate description generation | batch_69d4d7cada7881908beba55a1dc9ecb9 |
completed | April 7, 2026, 10:09 a.m. |
Created at: April 6, 2026, 11:41 a.m.