Triple
T4509351
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Demotic script |
E102009
|
entity |
| Predicate | scriptComplexity |
P28756
|
FINISHED |
| Object | highly ligatured and abbreviated |
—
|
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: highly ligatured and abbreviated | Statement: [Demotic script, scriptComplexity, highly ligatured and abbreviated]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scriptComplexity Context triple: [Demotic script, scriptComplexity, highly ligatured and abbreviated]
-
A.
parsingComplexity
Indicates the level of difficulty or computational effort required to parse or analyze a given input or structure.
-
B.
hasComplexity
chosen
Indicates that something possesses a certain level or type of complexity, often in terms of structure, behavior, or difficulty.
-
C.
hasReasoningComplexity
Indicates that an action, process, or decision involves a certain level or type of cognitive or logical complexity in its reasoning.
-
D.
scriptCode
Indicates that an entity is associated with a particular writing system or script, identified by a standardized script code.
-
E.
spaceComplexity
Indicates the relationship between an algorithm and the amount of memory it requires as a function of input size.
- 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_69bd43d6251c81909deecce3e6e9d69c |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd571138b88190b68bbfc4300aaf9d |
completed | March 20, 2026, 2:17 p.m. |
| PD | Predicate disambiguation | batch_69bd5218afb4819087c99e0a1f22e137 |
completed | March 20, 2026, 1:56 p.m. |
Created at: March 20, 2026, 1:01 p.m.