Triple
T4165887
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | axiom schema of separation |
E84443
|
entity |
| Predicate | introducedToSolve |
P513
|
FINISHED |
| Object | logical paradoxes in naive set theory |
—
|
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: logical paradoxes in naive set theory | Statement: [axiom schema of separation, introducedToSolve, logical paradoxes in naive set theory]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: introducedToSolve Context triple: [axiom schema of separation, introducedToSolve, logical paradoxes in naive set theory]
-
A.
aimsToSolve
Indicates an intention or purpose directed toward resolving, addressing, or eliminating a particular problem, challenge, or issue.
-
B.
basedOnSolutionOf
Indicates that one entity is derived, developed, or constructed using the solution or outcome produced by another entity.
-
C.
commonlySolvedBy
Indicates that a problem, task, or issue is typically addressed or resolved through a particular method, tool, or agent.
-
D.
introduced
chosen
Indicates that one entity caused another entity to become known, presented, or brought into use for the first time to a person, group, or context.
-
E.
solved
Indicates that one entity has successfully found a solution or answer to a problem, task, or challenge involving another entity.
- 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_69aed932cab48190b80ffe35f7029ae1 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69af02ac8e788190a8f3563a2903bbad |
completed | March 9, 2026, 5:26 p.m. |
| PD | Predicate disambiguation | batch_69af018fb0948190a9701b2e8e5d9bac |
completed | March 9, 2026, 5:21 p.m. |
Created at: March 9, 2026, 3:44 p.m.