Triple
T36471775
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New Kingdom Egyptian art |
E898554
|
entity |
| Predicate | hasNotablePhase |
P3574
|
FINISHED |
| Object | Amarna art |
E450252
|
NE 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: Amarna art | Statement: [New Kingdom Egyptian art, hasNotablePhase, Amarna art]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotablePhase Context triple: [New Kingdom Egyptian art, hasNotablePhase, Amarna art]
-
A.
hasNotableTransition
Indicates that an entity undergoes or is associated with a significant change, shift, or transformation in state, condition, or role.
-
B.
hasNotableSegment
chosen
Indicates that an entity includes or contains a specific segment, part, or portion that is considered notable or significant in some way.
-
C.
hasNotabilityPeriod
Indicates the time span during which an entity is or was notable or prominent.
-
D.
hasNotableOperation
Indicates that an entity is associated with a significant or noteworthy operation, activity, or procedure.
-
E.
hasNotableVersion
Indicates that an entity has a specific version or variant that is particularly significant, distinguished, or noteworthy compared to other versions.
- F. None of above.
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_69f76e58ebd88190b75d9b169b59d793 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a39cfd514d481908ec4e629f7d84232 |
completed | June 23, 2026, 12:14 a.m. |
| PD | Predicate disambiguation | batch_6a037a0bf4b88190bdcfae9a14b51f0a |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:10 p.m.