Triple
T31520204
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Loge |
E804186
|
entity |
| Predicate | relationshipToGods |
P60881
|
FINISHED |
| Object | ally and outsider |
—
|
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: ally and outsider | Statement: [Loge, relationshipToGods, ally and outsider]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationshipToGods Context triple: [Loge, relationshipToGods, ally and outsider]
-
A.
relationshipToDeities
chosen
Indicates how an entity is connected or related to one or more deities, such as through worship, lineage, role, or status.
-
B.
relatedNameOfGod
Indicates that one entity is a name, title, or designation that refers to or is associated with God.
-
C.
associatedWithGod
Indicates a relationship in which an entity is linked, related, or connected in some meaningful way to a god or deity.
-
D.
relationshipToReligion
Indicates the nature or type of connection an entity has to a religion, such as affiliation, stance, or involvement.
-
E.
relatedDeityFamily
Indicates a familial relationship between a deity and another entity, such as being a parent, child, sibling, or spouse within a divine family.
- 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_69f348cf839c81908657048402f7f97b |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379e7aa0c8190bdc9ee4d54fc821b |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 30, 2026, 9:55 p.m.