Triple
T8895470
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sin |
E211794
|
entity |
| Predicate | epithet |
P743
|
FINISHED |
| Object |
Lord of the Month
Lord of the Month is an epithet of the Mesopotamian moon god Sin, highlighting his divine authority over the lunar cycle and monthly time.
|
E765149
|
NE FINISHED |
How this triple was built (4 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: Lord of the Month | Statement: [Sin, epithet, Lord of the Month]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Lord of the Month Context triple: [Sin, epithet, Lord of the Month]
-
A.
Lord of Amerongen
Lord of Amerongen is a Dutch noble title historically associated with the aristocratic family of Amerongen in the Netherlands.
-
B.
Lord of Moy
Lord of Moy is a noble title historically associated with the French princely House of Lorraine.
-
C.
Lord of Lambesc
Lord of Lambesc is a noble title historically associated with a cadet branch of the influential French House of Lorraine.
-
D.
Lord of Baux
The Lord of Baux was the feudal ruler of the medieval Provençal stronghold of Les Baux, held by the influential House of Baux in southern France.
-
E.
Book of Lords
Book of Lords is the English rendering of the title of the Khwaday-Namag, a lost Middle Persian royal chronicle that recounted the legendary and historical kings of Iran.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Lord of the Month Triple: [Sin, epithet, Lord of the Month]
Generated description
Lord of the Month is an epithet of the Mesopotamian moon god Sin, highlighting his divine authority over the lunar cycle and monthly time.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Lord of the Month Target entity description: Lord of the Month is an epithet of the Mesopotamian moon god Sin, highlighting his divine authority over the lunar cycle and monthly time.
-
A.
Lord of Amerongen
Lord of Amerongen is a Dutch noble title historically associated with the aristocratic family of Amerongen in the Netherlands.
-
B.
Lord of Moy
Lord of Moy is a noble title historically associated with the French princely House of Lorraine.
-
C.
Lord of Lambesc
Lord of Lambesc is a noble title historically associated with a cadet branch of the influential French House of Lorraine.
-
D.
Lord of Baux
The Lord of Baux was the feudal ruler of the medieval Provençal stronghold of Les Baux, held by the influential House of Baux in southern France.
-
E.
Book of Lords
Book of Lords is the English rendering of the title of the Khwaday-Namag, a lost Middle Persian royal chronicle that recounted the legendary and historical kings of Iran.
- F. None of above. chosen
Provenance (5 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_69ca83918d3081909b326fa3750cb8c8 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc61be2c2081908f39cccdc149872d |
completed | April 1, 2026, 12:07 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cfac02974881908a7e8d9cfa47e624 |
completed | April 3, 2026, 12:01 p.m. |
| NEDg | Description generation | batch_69cfad512ad081908e046e9d95097071 |
completed | April 3, 2026, 12:06 p.m. |
| NED2 | Entity disambiguation (via description) | batch_69cfadf4c1fc81908df957dc0a6308dc |
completed | April 3, 2026, 12:09 p.m. |
Created at: March 30, 2026, 6:54 p.m.