Triple
T3780708
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | set theory |
E85409
|
entity |
| Predicate | hasFoundationIn |
P13223
|
FINISHED |
| Object | axiomatic systems |
—
|
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: axiomatic systems | Statement: [set theory, hasFoundationIn, axiomatic systems]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFoundationIn Context triple: [set theory, hasFoundationIn, axiomatic systems]
-
A.
hasFoundation
chosen
Indicates that an entity is supported, established, or based upon a particular foundation or underlying basis.
-
B.
foundedUnder
Indicates that an entity was established or created during the tenure, authority, or jurisdiction of another entity (such as a leader, regime, or governing body).
-
C.
foundedFor
Indicates that an entity was established or created specifically to serve, support, or benefit another entity or purpose.
-
D.
foundedWith
Indicates that an entity was established or created together with another entity, typically as co-founders or jointly initiated partners.
-
E.
foundingStatus
Indicates the relationship describing an entity’s role or condition in the creation or establishment of another entity (e.g., whether it is a founder, co-founder, or non-founder).
- 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_69aed937fa8881908208ef3801060826 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aee634c6ac819099653c660c286746 |
completed | March 9, 2026, 3:24 p.m. |
| PD | Predicate disambiguation | batch_69aee3d3c92c819081d9d5c45ef37a5d |
completed | March 9, 2026, 3:14 p.m. |
Created at: March 9, 2026, 3:12 p.m.