Triple
T35200588
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | At the Corner of Broadway + Soul |
E1016386
|
entity |
| Predicate | hasSoulInfluence |
P194101
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [At the Corner of Broadway + Soul, hasSoulInfluence, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSoulInfluence Context triple: [At the Corner of Broadway + Soul, hasSoulInfluence, yes]
-
A.
hasWorldSoul
Indicates that an entity possesses or is intrinsically connected to a fundamental, unifying spiritual essence of a world or cosmos.
-
B.
hasRitualInfluenceFrom
Indicates that one entity’s rituals, practices, or ceremonial traditions exert an influence on another entity’s rituals or ritual behavior.
-
C.
associatedWithSoulsOf
Indicates a relationship in which something is connected, linked, or related specifically to the souls of certain entities.
-
D.
hasSoulGemAbility
Indicates that an entity possesses the capability to use, interact with, or be affected by a soul gem and its associated powers or functions.
-
E.
levelInSoul
Indicates a relationship where an entity has a specific level, rank, or degree within a soul or soul-related state.
- F. None of above. chosen
Provenance (4 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_69f76dde814c8190a71f60d514a424a4 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fd5f29b1988190877764ef2a399c7f |
completed | May 8, 2026, 3:57 a.m. |
| PD | Predicate disambiguation | batch_69fd5e30194c819085b5ce586122ab37 |
completed | May 8, 2026, 3:53 a.m. |
| PDg | Predicate description generation | batch_69fd5f2903a48190ac4b718bff99c6cf |
completed | May 8, 2026, 3:57 a.m. |
Created at: May 3, 2026, 4:02 p.m.