Triple
T29949876
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | psychomagic |
E760737
|
entity |
| Predicate | prerequisiteConcept |
P152809
|
FINISHED |
| Object | symbolic thinking |
—
|
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: symbolic thinking | Statement: [psychomagic, prerequisiteConcept, symbolic thinking]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: prerequisiteConcept Context triple: [psychomagic, prerequisiteConcept, symbolic thinking]
-
A.
prerequisiteKnowledge
chosen
Indicates that one piece of knowledge must be acquired or understood before another can be effectively learned or applied.
-
B.
introducedConcept
Indicates that one entity is responsible for presenting, defining, or bringing a new concept into use or awareness for another entity or context.
-
C.
commonConcept
Indicates that two or more entities share the same underlying idea, notion, or conceptual meaning.
-
D.
detailsConcept
Indicates that one entity provides additional information, clarification, or elaboration about a concept represented by another entity.
-
E.
primaryConcept
Indicates that one concept is the main or central idea in relation to another concept 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_69f2246562b881909d57622f4086d43d |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f6780e8f408190a7186c21427926af |
completed | May 2, 2026, 10:17 p.m. |
| PD | Predicate disambiguation | batch_69f66ec8298c8190b41fe9d182c05676 |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 29, 2026, 6:25 p.m.