Triple
T30907742
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Solara |
E787348
|
entity |
| Predicate | religiousAwakening |
P59381
|
FINISHED |
| Object | inspired by Eli’s faith |
—
|
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: inspired by Eli’s faith | Statement: [Solara, religiousAwakening, inspired by Eli’s faith]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: religiousAwakening Context triple: [Solara, religiousAwakening, inspired by Eli’s faith]
-
A.
religiousTransmission
chosen
Indicates the passing on or spread of religious beliefs, practices, or traditions from one entity to another.
-
B.
religiousMotivation
Indicates that an action, decision, or relationship is driven or significantly influenced by religious beliefs, values, or obligations.
-
C.
religiousMood
Indicates a prevailing emotional or spiritual atmosphere associated with religious experience, practice, or devotion between entities.
-
D.
religiousElement
Indicates that something is a component, aspect, or feature associated with a religion or religious practice.
-
E.
religiousSpectrum
Indicates a relationship that places entities along a range or continuum of religious belief, practice, or affiliation.
- 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_69f224be300c8190a6513ce1ee0a7026 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fe6c811bcc81908b1e1b1f8bcb071b |
completed | May 8, 2026, 11:06 p.m. |
| PD | Predicate disambiguation | batch_69fe6c026d5481908b7a814dcf38c183 |
completed | May 8, 2026, 11:04 p.m. |
Created at: April 29, 2026, 8:50 p.m.