Triple
T29756
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mojave people |
E593
|
entity |
| Predicate | cosmology |
P450
|
FINISHED |
| Object | dream-based spiritual knowledge |
—
|
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: dream-based spiritual knowledge | Statement: [Mojave people, cosmology, dream-based spiritual knowledge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cosmology Context triple: [Mojave people, cosmology, dream-based spiritual knowledge]
-
A.
wasColonyOf
Indicates that one entity functioned as a colony under the political control or administration of another entity.
-
B.
causeOf
Indicates that one entity brings about, produces, or is responsible for the occurrence or existence of another entity or event.
-
C.
category
Indicates that one entity is classified as a member or type within the grouping or class defined by another entity.
-
D.
subjectMatter
chosen
Indicates the topic, theme, or content area that something (such as a work, document, or discussion) is about.
-
E.
theorized
Indicates that one entity has proposed or developed a theoretical explanation or hypothesis about another entity or phenomenon.
- 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_69a2479dec388190967ba648663442c9 |
completed | Feb. 28, 2026, 1:40 a.m. |
| NER | Named-entity recognition | batch_69a2490019948190a89bb0910c60d462 |
completed | Feb. 28, 2026, 1:46 a.m. |
| PD | Predicate disambiguation | batch_69a2486d40348190b2d21fc444f499a6 |
completed | Feb. 28, 2026, 1:44 a.m. |
Created at: Feb. 28, 2026, 1:44 a.m.