Triple
T6442893
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | S3 (Gardiner sign list) |
E138266
|
entity |
| Predicate | scriptStage |
P70672
|
FINISHED |
| Object | Classical Egyptian |
—
|
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: Classical Egyptian | Statement: [S3 (Gardiner sign list), scriptStage, Classical Egyptian]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scriptStage Context triple: [S3 (Gardiner sign list), scriptStage, Classical Egyptian]
-
A.
scriptPhase
Indicates that one process, event, or component occurs during a particular stage or phase of a larger scripted or planned sequence.
-
B.
stageName
Indicates that one entity is the performance or professional name used by another entity.
-
C.
stageConfiguration
Indicates the specific arrangement or setup of components, elements, or conditions at a particular stage within a process or system.
-
D.
stage
Indicates that an entity organizes, presents, or performs another entity (such as an event, show, or action) as a staged occurrence.
-
E.
script
Indicates that an entity is associated with a written text or code (such as a screenplay, program, or written instructions) that defines its content or behavior.
- 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_69c008aa61ac8190bc96715ed79fe2d8 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c0698b030481908b7bb4e16a8b3339 |
completed | March 22, 2026, 10:13 p.m. |
| PD | Predicate disambiguation | batch_69c060faaf248190bbdc8ff909c8777a |
completed | March 22, 2026, 9:36 p.m. |
| PDg | Predicate description generation | batch_69c0623e3cd48190929b0e3cba013909 |
completed | March 22, 2026, 9:42 p.m. |
Created at: March 22, 2026, 4:46 p.m.