Triple
T8733346
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hasse principle |
E207311
|
entity |
| Predicate | globalCondition |
P84545
|
FINISHED |
| Object | existence of a rational solution |
—
|
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: existence of a rational solution | Statement: [Hasse principle, globalCondition, existence of a rational solution]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: globalCondition Context triple: [Hasse principle, globalCondition, existence of a rational solution]
-
A.
coreCondition
Indicates that something serves as the primary or fundamental condition that must hold for a situation, process, or relationship to apply.
-
B.
presentCondition
Indicates that an entity currently has or exhibits a particular state, situation, or condition.
-
C.
conveningCondition
Indicates the circumstances or requirements under which a meeting, gathering, or formal session is initiated or brought together.
-
D.
operatingCondition
Indicates the specific state, requirements, or circumstances under which an entity functions or is intended to be used.
-
E.
captureCondition
Indicates the specific circumstances or criteria under which a capture event or action is triggered or considered valid.
- 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_69ca8358e4008190898471a59b96c301 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5d2a26988190acfda17f232e610a |
completed | March 31, 2026, 11:47 p.m. |
| PD | Predicate disambiguation | batch_69cc457322b481908712a9630a17b954 |
completed | March 31, 2026, 10:06 p.m. |
| PDg | Predicate description generation | batch_69cc572d99bc819097f36b140c2ee1ce |
completed | March 31, 2026, 11:22 p.m. |
Created at: March 30, 2026, 6:37 p.m.