Triple
T30551275
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amun division |
E777564
|
entity |
| Predicate | commandLanguageScript |
P180645
|
FINISHED |
| Object | hieroglyphic Egyptian (in official records) |
—
|
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: hieroglyphic Egyptian (in official records) | Statement: [Amun division, commandLanguageScript, hieroglyphic Egyptian (in official records)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commandLanguageScript Context triple: [Amun division, commandLanguageScript, hieroglyphic Egyptian (in official records)]
-
A.
scriptVariantLanguage
Indicates that a language is a variant distinguished by its writing system or script from another, related language form.
-
B.
scriptNameLanguage
Indicates that a script’s name is expressed or written in a particular language.
-
C.
usesScriptingLanguage
Indicates that an entity employs a scripting language to perform its operations, configuration, or automation tasks.
-
D.
scriptUsedForLanguage
Indicates that a particular writing script is employed to write or represent a given language.
-
E.
scriptLanguageIdentifier
Indicates the specific programming or scripting language associated with a given script or code artifact.
- 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_69f2249e19108190a458ab446096bf22 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f7465687bc8190a9da44d62b634ed7 |
completed | May 3, 2026, 12:57 p.m. |
| PD | Predicate disambiguation | batch_69f743f4ceb08190a21fe7f4a99b166b |
completed | May 3, 2026, 12:47 p.m. |
| PDg | Predicate description generation | batch_69f74654c09c819084879162eba9d641 |
completed | May 3, 2026, 12:57 p.m. |
Created at: April 29, 2026, 8:20 p.m.