Triple
T28667469
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Outer Gods |
E725621
|
entity |
| Predicate | relationToHumans |
P8492
|
FINISHED |
| Object | beyond human understanding |
—
|
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: beyond human understanding | Statement: [Outer Gods, relationToHumans, beyond human understanding]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationToHumans Context triple: [Outer Gods, relationToHumans, beyond human understanding]
-
A.
relationshipToHumans
chosen
Indicates the nature or type of connection, association, or relevance that something has specifically with humans.
-
B.
relationshipToRelative
Indicates the specific familial connection or kinship role that one person has in relation to a particular relative.
-
C.
relationToBabo
Indicates a relationship or connection that an entity has to the person or entity referred to as "Babo."
-
D.
relationshipToParents
Indicates the type or nature of a person's familial relationship to their parents.
-
E.
subjectFamilyRelation
Indicates that there is a familial relationship of some kind between the subject entity and 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_69f01d85be388190b669a0e401e2f2c4 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_6a004a8892c08190bcacb952ad737716 |
completed | May 10, 2026, 9:06 a.m. |
| PD | Predicate disambiguation | batch_6a004a44b4948190be4b3dbfce8da020 |
completed | May 10, 2026, 9:05 a.m. |
Created at: April 28, 2026, 5:01 a.m.