Triple
T8442878
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tam Phủ |
E199590
|
entity |
| Predicate | hasPantheonLevel |
P27705
|
FINISHED |
| Object | high-ranking female deities |
—
|
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: high-ranking female deities | Statement: [Tam Phủ, hasPantheonLevel, high-ranking female deities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPantheonLevel Context triple: [Tam Phủ, hasPantheonLevel, high-ranking female deities]
-
A.
hasPantheonName
Indicates that an entity is associated with a specific pantheon and is identified by the given pantheon name.
-
B.
positionInPantheon
chosen
Indicates the rank, role, or hierarchical standing that a deity or figure holds within a specific pantheon or religious hierarchy.
-
C.
convertedToPantheon
Indicates that something has been transformed or repurposed into a pantheon, typically changing its function or status to that of a sacred or monumental temple.
-
D.
hasLevel
Indicates that an entity possesses or is associated with a particular degree, rank, or stage within an ordered scale or hierarchy.
-
E.
honorLevel
Indicates the degree or status of respect, distinction, or recognition accorded to an entity relative to others.
- 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_69ca83170f9081909cd98f55614c6476 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe310d8e08190b871bda79acde678 |
completed | March 31, 2026, 3:06 p.m. |
| PD | Predicate disambiguation | batch_69cbd0f5a3648190beb53a139a2d5482 |
completed | March 31, 2026, 1:49 p.m. |
Created at: March 30, 2026, 6:08 p.m.