Triple
T124059
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Principia Mathematica |
E2507
|
entity |
| Predicate | addressesProblem |
P3847
|
FINISHED |
| Object | set-theoretic paradoxes |
—
|
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: set-theoretic paradoxes | Statement: [Principia Mathematica, addressesProblem, set-theoretic paradoxes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: addressesProblem Context triple: [Principia Mathematica, addressesProblem, set-theoretic paradoxes]
-
A.
addressesIssue
chosen
Indicates that one entity deals with, responds to, or attempts to resolve a specific issue associated with another entity.
-
B.
addresses
Indicates that one entity directs speech, communication, or written correspondence specifically toward another entity.
-
C.
issues
Indicates that an entity formally produces, releases, or distributes something, such as a document, order, or resource, making it officially available.
-
D.
address
Indicates that one entity directs spoken or written communication specifically to another entity.
-
E.
worksOnIssue
Indicates that an entity (typically a person or team) is actively engaged in addressing, resolving, or contributing work toward a specific issue.
- 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_69a251b54ea88190b18281669f59b4c0 |
completed | Feb. 28, 2026, 2:23 a.m. |
| NER | Named-entity recognition | batch_69a2573ce0ac8190b49fb31d3d475bf9 |
completed | Feb. 28, 2026, 2:47 a.m. |
| PD | Predicate disambiguation | batch_69a2564a54948190ba30bee858173b27 |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:27 a.m.