Triple
T27347852
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | King of Salem |
E684275
|
entity |
| Predicate | explainsIdea |
P5130
|
FINISHED |
| Object | Soul of the World |
—
|
NE NERFINISHED |
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: Soul of the World | Statement: [King of Salem, explainsIdea, Soul of the World]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: explainsIdea Context triple: [King of Salem, explainsIdea, Soul of the World]
-
A.
coreIdea
Indicates the central concept or primary message that underlies or unifies something, such as a text, argument, or work.
-
B.
aimsToExplain
chosen
Indicates that one entity intends to clarify, make understandable, or provide an explanation about another entity, concept, or situation.
-
C.
anticipatesIdeaIn
Indicates that one entity expects, predicts, or foresees the idea or concept that will be introduced or held by another entity in a given context.
-
D.
developsIdeasOf
Indicates that one entity creates, elaborates, or advances ideas that originate from or are associated with another entity.
-
E.
introducedConcept
Indicates that one entity is responsible for presenting, defining, or bringing a new concept into use or awareness for another entity or context.
- 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_69ef1480a76481908684256ddd5bfda3 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f63fd6c68481908c542aa03e297b9c |
completed | May 2, 2026, 6:17 p.m. |
| PD | Predicate disambiguation | batch_69f63c663be481908f233d25d28713a4 |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 27, 2026, 11:46 a.m.