Triple
T1266613
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | von Neumann–Bernays–Gödel set theory |
E15613
|
entity |
| Predicate | wasRefinedBy |
P4448
|
FINISHED |
| Object | Paul Bernays in the 1930s |
—
|
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: Paul Bernays in the 1930s | Statement: [von Neumann–Bernays–Gödel set theory, wasRefinedBy, Paul Bernays in the 1930s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasRefinedBy Context triple: [von Neumann–Bernays–Gödel set theory, wasRefinedBy, Paul Bernays in the 1930s]
-
A.
hasRefinement
chosen
Indicates that one entity represents a more detailed, specific, or improved version of another entity.
-
B.
wasUsedBy
Indicates that something served as a tool, resource, or means for an agent to perform an action or achieve a result.
-
C.
usedToSearchFor
Indicates that one entity serves as a tool, method, or resource employed to look for, locate, or retrieve another entity.
-
D.
curatedBy
Indicates that something has been selectively organized, managed, or assembled by a particular agent or entity.
-
E.
wantedBy
Indicates that one entity is desired, sought, or wished for by 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_69a4935a94308190bb92555b79032824 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4c037f14c8190baa42f70f8846583 |
completed | March 1, 2026, 10:39 p.m. |
| PD | Predicate disambiguation | batch_69a4bede52a081909665d60acbe41d31 |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:50 p.m.