Triple
T5114194
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arrow’s impossibility theorem |
E115290
|
entity |
| Predicate | axiom |
P12252
|
FINISHED |
| Object | unrestricted domain |
—
|
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: unrestricted domain | Statement: [Arrow’s impossibility theorem, axiom, unrestricted domain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: axiom Context triple: [Arrow’s impossibility theorem, axiom, unrestricted domain]
-
A.
foundationAxiomHoldsIn
Indicates that the foundation (or regularity) axiom is satisfied within a given model, structure, or context.
-
B.
hasAxiom
chosen
Indicates that an entity is associated with, defined by, or governed through a specific axiom or set of axioms.
-
C.
premise
Indicates that a statement or proposition provides the foundational assumption or starting point from which a conclusion or inference is logically derived.
-
D.
assumes
Indicates that one entity takes on, accepts, or presumes a role, responsibility, state, or fact regarding another entity or situation.
-
E.
logicSystem
Indicates a relationship where an entity is associated with, defined within, or governed by a particular logical framework or system of formal reasoning.
- 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_69bd4441d1648190a54a533895041987 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd75cd13a08190b53e67ba65333557 |
completed | March 20, 2026, 4:29 p.m. |
| PD | Predicate disambiguation | batch_69bd715fe3a8819087d3065adddba515 |
completed | March 20, 2026, 4:10 p.m. |
Created at: March 20, 2026, 1:41 p.m.