Triple
T3913081
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | axiom of choice |
E87367
|
entity |
| Predicate | domainOfDiscourse |
P26078
|
FINISHED |
| Object | collections of nonempty sets |
—
|
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: collections of nonempty sets | Statement: [axiom of choice, domainOfDiscourse, collections of nonempty sets]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: domainOfDiscourse Context triple: [axiom of choice, domainOfDiscourse, collections of nonempty sets]
-
A.
discourse
Indicates that one entity engages in extended verbal or written communication or discussion with another entity.
-
B.
notationDomain
Indicates a relationship where a notation system is associated with, or defined over, a particular domain in which it is valid or applicable.
-
C.
assumptionOnDomain
chosen
Indicates that a particular assumption or constraint is specified to hold over a given domain or set of entities.
-
D.
allegoricalDomain
Indicates that one entity serves as the abstract or symbolic domain that another entity allegorically represents or refers to.
-
E.
realm
Indicates that one entity is a domain, sphere of influence, or area of control associated with 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_69aed9424514819086e9c58adde6652d |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aef188b474819087680db42b04ecdd |
completed | March 9, 2026, 4:12 p.m. |
| PD | Predicate disambiguation | batch_69aee75eedcc81908088ff4dbb8be56b |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:22 p.m.