Triple
T3913041
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | axiom of choice |
E87367
|
entity |
| Predicate | statusInZFC |
P52531
|
FINISHED |
| Object | axiom of Zermelo–Fraenkel set theory with 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: axiom of Zermelo–Fraenkel set theory with choice | Statement: [axiom of choice, statusInZFC, axiom of Zermelo–Fraenkel set theory with choice]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusInZFC Context triple: [axiom of choice, statusInZFC, axiom of Zermelo–Fraenkel set theory with choice]
-
A.
status
Indicates the current condition, state, or standing of an entity within a given context.
-
B.
statusInLogic
Indicates the logical status or role an entity holds within a formal reasoning or inference context.
-
C.
designationStatus
Indicates the current official classification or standing assigned to an entity within a defined system or process.
-
D.
statusIndicates
Indicates that a particular status value conveys or reflects the current condition, state, or situation of an entity or process.
-
E.
deFactoStatus
Indicates that one entity holds a role, position, or status in practice or by custom, even if it is not formally or legally recognized.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69aef18748648190b85e62f7796ff4b4 |
completed | March 9, 2026, 4:12 p.m. |
Created at: March 9, 2026, 3:22 p.m.