Triple
T17971085
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aten |
E449339
|
entity |
| Predicate | relationshipToRa |
P129958
|
FINISHED |
| Object | aspect or manifestation of the sun god Ra |
—
|
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: aspect or manifestation of the sun god Ra | Statement: [Aten, relationshipToRa, aspect or manifestation of the sun god Ra]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationshipToRa Context triple: [Aten, relationshipToRa, aspect or manifestation of the sun god Ra]
-
A.
relationshipToRelative
Indicates the specific familial connection or kinship role that one person has in relation to a particular relative.
-
B.
relationshipToHumans
Indicates the nature or type of connection, association, or relevance that something has specifically with humans.
-
C.
relationshipType
Indicates the specific kind of relationship that exists between two or more entities.
-
D.
relationshipToARP
Indicates a specified type of relationship or association that an entity has to an ARP (which may represent a particular person, program, plan, or reference point).
-
E.
relationshipToState
Indicates a relationship or connection that an entity has with a particular state or governmental body.
- 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_69d8b9f9927c8190a006110c8b996e61 |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e4b1fa67c48190936f20cea45e4599 |
completed | April 19, 2026, 10:44 a.m. |
| PD | Predicate disambiguation | batch_69e3f8fa62688190a5d5c361ab896256 |
completed | April 18, 2026, 9:34 p.m. |
| PDg | Predicate description generation | batch_69e42d8d68288190a05dc5d7803cf823 |
completed | April 19, 2026, 1:19 a.m. |
Created at: April 10, 2026, 10:22 a.m.