Triple
T31883368
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CHIC (Corpus Hieroglyphicarum Inscriptionum Cretae) |
E813939
|
entity |
| Predicate | scriptTypeDocumented |
P4427
|
FINISHED |
| Object | Cretan hieroglyphic |
—
|
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: Cretan hieroglyphic | Statement: [CHIC (Corpus Hieroglyphicarum Inscriptionum Cretae), scriptTypeDocumented, Cretan hieroglyphic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scriptTypeDocumented Context triple: [CHIC (Corpus Hieroglyphicarum Inscriptionum Cretae), scriptTypeDocumented, Cretan hieroglyphic]
-
A.
scriptType
chosen
Indicates the classification or category of a script, specifying what kind of script it is (e.g., its format, purpose, or scripting language type).
-
B.
scriptTypeWorkedOn
Indicates the type or category of script that an entity has worked on or contributed to.
-
C.
DOCType
Indicates the type or category of a document associated with an entity or action.
-
D.
scriptDeclared
Indicates that a script has been explicitly defined or specified for an entity or within a given context.
-
E.
documentationType
Indicates the specific category or kind of documentation associated with or required for an entity or process.
- 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_69f348ed74bc81909846aaa6a3c7318c |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f7b2f3a104819098ddd8909eaf596c |
completed | May 3, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69f7b1b8a9fc8190a1279e67a2d12707 |
completed | May 3, 2026, 8:36 p.m. |
Created at: April 30, 2026, 11:56 p.m.