Triple
T32385469
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clerical Script |
E827533
|
entity |
| Predicate | complexityComparedToSealScript |
P179265
|
FINISHED |
| Object | more simplified |
—
|
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: more simplified | Statement: [Clerical Script, complexityComparedToSealScript, more simplified]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: complexityComparedToSealScript Context triple: [Clerical Script, complexityComparedToSealScript, more simplified]
-
A.
scriptOnSeal
Indicates that written characters or inscriptions are present on the surface of a seal.
-
B.
hasComplexity
Indicates that something possesses a certain level or type of complexity, often in terms of structure, behavior, or difficulty.
-
C.
isSealOf
Indicates that one entity serves as the official seal, emblem, or stamp that authenticates, endorses, or formally represents another entity.
-
D.
hasReasoningComplexity
Indicates that an action, process, or decision involves a certain level or type of cognitive or logical complexity in its reasoning.
-
E.
decryptionComplexity
Indicates the level of computational effort or difficulty required to decrypt data protected by a given cryptographic method or key.
- 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_69f349184e7481909c6c54428cb9cf12 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f7201e241c819092d56a7bb99dc94d |
completed | May 3, 2026, 10:14 a.m. |
| PD | Predicate disambiguation | batch_69f71cc405c08190863565609a4c8499 |
completed | May 3, 2026, 10 a.m. |
| PDg | Predicate description generation | batch_69f71f8df5d48190944fbfbd9d573868 |
completed | May 3, 2026, 10:12 a.m. |
Created at: May 1, 2026, 12:51 a.m.