Triple
T5992264
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maat |
E133376
|
entity |
| Predicate | heartWeighedAgainst |
P41135
|
FINISHED |
| Object | feather of Maat |
—
|
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: feather of Maat | Statement: [Maat, heartWeighedAgainst, feather of Maat]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heartWeighedAgainst Context triple: [Maat, heartWeighedAgainst, feather of Maat]
-
A.
ifHeartLighterThanFeather
chosen
Indicates that a heart is judged to be lighter than a feather, typically signifying moral purity or worthiness in a comparative evaluation.
-
B.
weight
Indicates a relationship where a numerical value quantifies how heavy an entity is, often used to measure or compare mass or load.
-
C.
weightIssue
Indicates that there is a problem, concern, or abnormal condition related to the weight of an entity.
-
D.
isHeavilyWeightedToward
Indicates that something is strongly biased or disproportionately oriented in favor of one side, option, or aspect over others.
-
E.
heartNote
Indicates that one entity records or expresses a heartfelt or emotionally significant note or message about another entity.
- F. None of above.
Provenance (3 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_69c0087010d081908bb8142342d63330 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c04e8fd030819095a4f3b3d425ec21 |
completed | March 22, 2026, 8:18 p.m. |
| PD | Predicate disambiguation | batch_69c049e152e88190979ab80cb9b50321 |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:05 p.m.