Triple
T3214017
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spinozism |
E67347
|
entity |
| Predicate | hasViewOnMindBody |
P46236
|
FINISHED |
| Object | mind–body parallelism |
—
|
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: mind–body parallelism | Statement: [Spinozism, hasViewOnMindBody, mind–body parallelism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasViewOnMindBody Context triple: [Spinozism, hasViewOnMindBody, mind–body parallelism]
-
A.
hasListingVenue
Indicates that an item, event, or offering is associated with the specific venue where it is listed or made available.
-
B.
hasBusinessTypeAlong
Indicates that a business or commercial entity located along a route, corridor, or area is associated with a specific type or category of business activity.
-
C.
hasBusiness
Indicates that one entity owns, operates, or is formally associated with a business entity.
-
D.
siteTypeServed
Indicates the type of site or location that is served, supported, or handled by a given entity or resource.
-
E.
isReferralCenterFor
Indicates that one entity serves as a designated center to which other entities send or direct cases, clients, or tasks for specialized services or handling.
- 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_69ad858ac36c81909962589cd277d6e2 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69adaabd01d48190be0dc610b9987a25 |
completed | March 8, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69ad9e09b83881908801d79c3d9254f9 |
completed | March 8, 2026, 4:04 p.m. |
| PDg | Predicate description generation | batch_69ada0f9259c8190afbc5ad0fa55436b |
completed | March 8, 2026, 4:16 p.m. |
Created at: March 8, 2026, 3:07 p.m.