Triple
T3913075
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | axiom of choice |
E87367
|
entity |
| Predicate | hasWeakerForm |
P24324
|
FINISHED |
| Object | countable axiom of choice |
—
|
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: countable axiom of choice | Statement: [axiom of choice, hasWeakerForm, countable axiom of choice]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWeakerForm Context triple: [axiom of choice, hasWeakerForm, countable axiom of choice]
-
A.
weakerThan
chosen
Indicates that one entity has less strength, power, or effectiveness than another entity.
-
B.
strongerThan
Indicates that one entity possesses greater strength, power, or intensity than another.
-
C.
hasWeakness
Indicates that one entity is vulnerable to, or can be adversely affected or defeated by, another entity.
-
D.
formsWeakDoubletWith
Indicates that one entity forms a weakly interacting or loosely coupled pair (doublet) with another entity, typically in contrast to a stronger or more tightly bound association.
-
E.
hasLowercaseForm
Indicates that one entity is the lowercase version or representation of 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.