Triple
T19790902
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | cult of Min |
E475406
|
entity |
| Predicate | devotedTo |
P8131
|
FINISHED |
| Object | Min |
—
|
NE NERFINISHED |
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: Min | Statement: [cult of Min, devotedTo, Min]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Min Context triple: [cult of Min, devotedTo, Min]
-
A.
Min
chosen
Min is an ancient Egyptian fertility and male potency god, often depicted as a mummified man with an erect phallus and associated with procreation, harvests, and the eastern desert.
-
B.
Min
Min is a major branch of the Chinese language family, encompassing diverse regional varieties spoken primarily in Fujian, Taiwan, and among overseas Chinese communities.
-
C.
Min
Min is a common given name of Chinese origin used for both males and females.
-
D.
Min
Min is a Chinese surname that is relatively uncommon and can be represented by several different Chinese characters.
-
E.
Min
Min is a common place name element used in various geographic locations, often derived from local linguistic or historical origins.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8e51b014081908b263e167370529a |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e653c217bc819092c517b27ca22087 |
completed | April 20, 2026, 4:26 p.m. |
Created at: April 10, 2026, 1:49 p.m.